Signing in
Sign in to the Urlbox MCP server with your Urlbox account, manage connections, and choose which project renders use. API keys are a fallback for headless use.
Agents connect to https://api.urlbox.com/mcp by signing in with your Urlbox account. There is no key to create or paste. Claude, ChatGPT, Claude Code, Codex, Cursor, VS Code and any other client that supports OAuth for remote MCP servers sign in this way; see Connect your agent for each client's steps.
What the sign-in asks
When you add the server, your client opens Urlbox in your browser. You:
- Sign in to Urlbox.
- Choose the organisation to connect.
- Choose an access level: Full access, Render and read, or Read only. The agent only sees tools that access allows; anything else is left out of its tool list rather than returned as an error.
- Choose a default project, which renders use when the agent does not name one.
- Approve the connection. Check that the name shown is the client you are connecting.
Only organisation owners and admins can connect a client. A connection is checked again on every request.
Managing connections
You can see and revoke connections under Organisation settings, AI agents, alongside any agents set up with a key. Revoking a connection cuts the client off at once; to use it again, sign in again.
Which project renders use
Every render tool takes an optional project, a project id (proj_…) or exact name. When the agent leaves it out, the render uses the default project chosen when you signed in. list_projects shows the projects the agent can use and marks its default.
If the default project is later disabled, renders that do not name a project are refused with ProjectDisabled until the agent names an enabled project or you sign in again with a new default. If the default project is deleted, renders fall back to the organisation's oldest enabled project.
Using an API key instead
For headless and CI use, or a client without OAuth support, an agent can send a key in an Authorization: Bearer <key> header instead of signing in:
- Organisation API key: create one under Organisation settings, API keys (owners and admins). You pick its access level and default project when you create it, as with sign-in. Keys start with
ubx_org_. - Project secret key: works for the render tools only (plus
get_renderfor that project's renders anddescribe_options), and renders into its own project.
Keep keys out of anything you commit. Key-based setup for each client is under Using an API key instead.