Connect your agent

Urlbox runs a remote MCP server, so any MCP client can call it directly. There is no local server to run and no key to copy: you add the URL and sign in with your Urlbox account.

• Address: https://api.urlbox.com/mcp
• Transport: Streamable HTTP
• Auth: sign in with your Urlbox account (OAuth). No key needed.

Connect to the Urlbox MCP server at https://api.urlbox.com/mcp using OAuth sign-in (no API key).
Detect which agent you are and run the right command (or edit the right config file) to add it under the name "urlbox" as a Streamable HTTP server, then tell me how to authenticate so I can sign in with my Urlbox account.
Once I have signed in, list its tools to confirm it works.
Setup for each client: https://urlbox.com/docs/agents/mcp

Add the URL and sign in

Pick your client, then copy its command or config. None of them needs a key: each one connects with just the URL and asks you to sign in with your Urlbox account.

https://api.urlbox.com/mcp

https://api.urlbox.com/mcp

claude mcp add --transport http --scope user urlbox https://api.urlbox.com/mcp

codex mcp add urlbox --url https://api.urlbox.com/mcpcodex mcp login urlbox

{  "mcpServers": {    "urlbox": {      "url": "https://api.urlbox.com/mcp"    }  }}

{  "servers": {    "urlbox": {      "type": "http",      "url": "https://api.urlbox.com/mcp"    }  }}

code --add-mcp '{"name":"urlbox","type":"http","url":"https://api.urlbox.com/mcp"}'

gemini mcp add --transport http --scope user urlbox https://api.urlbox.com/mcp

{  "mcpServers": {    "urlbox": {      "serverUrl": "https://api.urlbox.com/mcp"    }  }}

{  "mcpServers": {    "urlbox": {      "serverUrl": "https://api.urlbox.com/mcp"    }  }}

{  "context_servers": {    "urlbox": {      "url": "https://api.urlbox.com/mcp"    }  }}

{  "$schema": "https://opencode.ai/config.json",  "mcp": {    "urlbox": {      "type": "remote",      "url": "https://api.urlbox.com/mcp",      "enabled": true    }  }}

URL: https://api.urlbox.com/mcpTransport: Streamable HTTPAuth: OAuth (sign in when asked)

Claude Code scopes and plugin

claude mcp add takes a --scope:

You can also install the Urlbox plugin for Claude Code, which adds the same server plus Urlbox skills:

claude plugin marketplace add urlbox/claude-plugin
claude plugin install urlbox@urlbox

Then run /mcp, pick urlbox and choose Authenticate to sign in.

What the sign-in asks

Signing in opens Urlbox in your browser, where you:

1. Sign in to Urlbox.
2. Choose the organisation, an access level (Full access, Render and read or Read only) and a default project for renders.
3. Approve the connection. Check that the name shown is the client you are connecting.

Only organisation owners and admins can connect a client. You can see and revoke connections under Organisation settings, AI agents. See Signing in for more.

Clients that only run local servers

Some MCP clients can only start local servers and cannot connect to a remote URL. For those, use the @urlbox/screenshot-mcp npm package. From version 2.0 it is a thin local bridge that forwards every request to https://api.urlbox.com/mcp, so you get the same tools. Setup is in its README on GitHub.

Using an API key instead

For headless and CI use, or a client without OAuth support, send a key in an Authorization: Bearer <key> header instead of signing in:

• An organisation API key, created under Organisation settings, API keys, with the access and default project you pick there.
• A project secret key also works, for the render tools only.

Warp is set up this way too: its docs do not cover signing in to other MCP servers, so use an organisation API key there.

The dashboard's Connect your agent button (under Organisation settings, API keys) fills in a key-based setup for your client. See Signing in for what each key can do.

Troubleshooting

• 401 Unauthorized: the Authorization header is missing, or the key is wrong or has been revoked. Sign in again, or reconnect with a current key.
• 403 Forbidden: the key is valid but cannot render: the account is not active, the key's project is disabled, or the organisation has no enabled project. The response says which.
• 429 Too Many Requests: the key has hit a request limit. When the response carries a Retry-After header, wait that many seconds before trying again.
• A tool you expect is missing: the access level chosen when you signed in (or the key's access) does not include it. A project secret key only gets the render tools, get_render and describe_options. Check the key's access in the dashboard, or sign in again and choose Full access.
• InvalidOptions: an argument is missing or wrong. The message names it. The most common case is a missing, too short (under 10 characters) or too long (over 500) intent.
• RateLimited: too many requests too quickly. The error includes a retry delay; wait and try again.
• ProjectDisabled: the project you named is disabled. Enable it in the dashboard, or pick another project with list_projects.
• ProjectNotFound: the key cannot use the project you named. A project secret key can only render with its own project.
• UsageExceeded: the organisation has used up its plan's render allowance for the period. Check the usage tool or the dashboard's usage page.