Guide
Run Claude Code on your connect0 core
Three commands to point Claude Code at your connect0 core and let it run shell commands on your connected data, in an isolated per-project sandbox.
5/19/2026 · connect0 · 3 min
Point any MCP agent — here, Claude Code — at your connect0 core and let it run shell commands in an isolated sandbox on your data.
1. Register the MCP server
claude mcp add --transport http connect0 https://mcp.connect0.ai
Claude Code stores the registration in its config and uses it on the next /mcp prompt.
2. Sign in
In Claude Code, run /mcp. Claude Code opens a browser, you complete the OAuth dance against auth.connect0.ai, and the credentials are saved. The handshake happens once per machine.
3. Run shell commands
Talk to the agent normally:
"Run
pnpm installin my demo project."
Claude Code calls info to find your account + project slugs, then sh with the command. Output streams back. Workspace state — anything written to /workspace — persists between calls.
What can go wrong
- No accounts yet?
infowill reportnext_step: "account.create". Tell the agent "create an account called Acme" and it'll call the right tool. - No projects yet? Same pattern —
next_step: "project.create". - Egress blocked? Default is
restricted. From/app/<account>/projects/<project>you can flipegresstoopenif you needapt-get installto reach the public internet.
Next steps
- Set up Cursor — same backend, different client.
- Manage projects in the dashboard.
Where this fits
This is the Run your agents pillar of connect0 — the core that connects everything your company runs on. Claude Code becomes an agent running on the core: it calls sh in an isolated per-project sandbox and acts on the workspace connect0 keeps for you. Start building → · All guides →