MCP clients
Connect Claude Code, Codex, ChatGPT, or another agent to your Arc0 account.
Start by signing in to Arc0 and connecting GitHub in My apps. Then open Arc0 MCP and copy your server URL. For hosted Arc0, it is:
https://api.arc0.ai/mcpChoose OAuth for interactive clients. Sign in to Arc0, select your workspace, review access, and approve it. This authorizes your agent to use Arc0; GitHub's connection consent is separate. Your agent can use only the tools and accounts allowed for that identity.
Claude Code
Register Arc0 for your user across projects:
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpOpen Claude Code, enter /mcp, select Arc0, and authenticate. Finish sign-in and
consent in your browser, then return to Claude Code. Check that Arc0 shows as
connected. You can also inspect it with claude mcp get arc0.
If a server named arc0 already exists, inspect its URL before changing it. Do not
replace another setup or delete its stored credentials just to retry a failed call.
See the official Claude Code MCP guide.
Codex app and CLI
The Codex app and CLI share MCP configuration in ~/.codex/config.toml. Register
Arc0 from your terminal:
codex mcp add arc0 --url https://api.arc0.ai/mcpComplete the browser OAuth flow, choose your Arc0 workspace, and review access. If authentication does not start, run:
codex mcp login arc0Check the configured server with codex mcp list. Open a new Codex chat after setup
and try the read below. No Arc0 API key is needed. If arc0 already exists, inspect
its URL before changing it; preserve other MCP servers and stored credentials.
See the official Codex MCP guide.
ChatGPT
Use ChatGPT on the web:
- Open Plugins, select the plus button, then Add custom MCP server.
- Name it Arc0 and enter
https://api.arc0.ai/mcpas the server URL. - Choose OAuth. If asked about client registration, use dynamic client registration; you do not need to supply an Arc0 API key or your GitHub OAuth app credentials.
- Review ChatGPT's notice and select Create as a plugin. Complete the Arc0 sign-in, workspace selection, and consent flow when prompted.
- Install the resulting plugin and select it in your conversation before making a request.
Labels and availability can vary by account. A managed workspace may require its administrator to allow custom MCP apps. Follow the current OpenAI setup guide if your interface differs. Choose OAuth rather than mixed or unauthenticated access: Arc0 requires authentication for initialization and tool discovery.
Browse MCP client guides for app availability and client-specific directories.
Try your first read
After connecting GitHub and authorizing your client, send:
Use Arc0 to find the GitHub profile action, load its schema, and read my connected GitHub profile. Do not make any changes.
The agent should discover github.get_profile, retrieve its exact schema and version,
and execute the read. Open Activity in Arc0 to inspect the receipt. A connected
client confirms MCP authentication; a successful receipt confirms the provider call.
If no GitHub action appears, check that GitHub and its tool access are enabled for the selected identity. If a connection is required, complete the hosted connection flow. If multiple accounts are available, choose the intended account explicitly.
Other clients and API keys
For another interactive client, add the same URL through its remote MCP settings and use OAuth. The client must reach both Arc0's API and authorization server.
For clients without OAuth support, use a self-bound API key with execute permission.
Add connect permission if the agent should request hosted connection links. Keep the
key in the client's secret storage or an environment variable, outside source control.
import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js';
const client = new Client({ name: 'my-agent', version: '1.0.0' });
await client.connect(new StreamableHTTPClientTransport(
new URL(process.env.ARC0_MCP_URL!),
{ requestInit: { headers: { 'x-api-key': process.env.ARC0_API_KEY! } } },
));
const tools = await client.listTools();The header is X-API-Key. Bearer tokens are reserved for OAuth; never send both.
Unbound business management keys are rejected by MCP. Businesses should follow
Embedded identity to link an end user before OAuth or mint
a self-bound runtime key.
Troubleshooting and local development
- Needs authentication: complete the client's OAuth flow; adding the URL alone does not finish setup.
- No workspace available: create a personal workspace in Arc0, or finish the business's account-link flow, then retry authorization.
- Wrong workspace: revoke the agent's authorization in Arc0 MCP and authorize the intended workspace. Changing a URL cannot switch identities.
- Timed-out action: retrieve its execution receipt before retrying. Keep the same idempotency key for an unchanged request.
Local developers can use http://localhost:4312/mcp with a locally running client.
Hosted clients cannot reach your laptop's localhost URL. Use hosted Arc0 for ChatGPT;
local acceptance does not prove hosted-client compatibility.