Quickstart
Connect GitHub and make your first read through an AI agent.
Connect an app once, then let your agent use it through Arc0. This walkthrough uses a personal account, GitHub, and OAuth. You do not need to create an API key.
1. Create your personal workspace
Open Arc0, create an account or sign in, and choose a personal workspace. Personal workspaces keep your connected accounts private to you and do not require project, environment, or end-user configuration.
2. Connect GitHub
Open My apps, choose GitHub and OAuth, and follow the hosted connection link. Review GitHub's consent screen and authorize the intended account. Return to Arc0 and confirm that the connection is active.
The current GitHub adapter requests fixed read:user repo scopes. Review that access
before approving it. Arc0's action permissions still govern what your agent may do.
See GitHub for the supported actions and connection behavior.
3. Connect your agent
Open Arc0 MCP and copy the server URL:
https://api.arc0.ai/mcpFor Claude Code:
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpEnter /mcp in Claude Code, select Arc0, and complete OAuth. Choose your personal
workspace and review access before approving it.
For the Codex app or CLI, add Arc0 from your terminal and complete browser OAuth:
codex mcp add arc0 --url https://api.arc0.ai/mcpIf sign-in does not start, run codex mcp login arc0. Open a new Codex chat after setup.
For ChatGPT, add the URL as a custom MCP server with OAuth, install the resulting plugin, and select it in your conversation. See MCP clients for the current setup and verification steps.
4. Make a safe first call
Ask your agent:
Use Arc0 to find the GitHub profile action, load its schema, and read my connected GitHub profile. Do not make any changes.
Open Activity to inspect the execution receipt. If the agent finds no GitHub tool, check GitHub's tool access in My apps. A missing or expired connection must be connected or reconnected before an authenticated read can succeed.
Building a product for your users?
Choose a business workspace for Embedded use. Enable an app in your concrete project, create an end user, and issue a hosted connection link bound to that user. Link the user's Arc0 identity before authorizing an interactive MCP client, or mint a self-bound runtime key. An unbound management key cannot authenticate to MCP.
Start with Build with your coding agent. Follow Embedded identity, the SDK guide, and the API reference for the current contracts. Development and Production are separate project rows: a Development project can still reach real provider accounts, so use a dedicated test account and review any provider writes.