Claude Code
Claude Code connects to remote MCP servers over HTTP, so it talks to Orbismo directly. You can connect either way:
- The connector (recommended) — sign in once and reach every world you grant, switching between them in conversation.
- A single world with an API key — pin Claude Code to one world with a bearer token.
The connector (recommended)
Section titled “The connector (recommended)”-
Add the connector server:
Terminal window claude mcp add --transport http orbismo https://app.orbismo.com/api/v1/mcp -
In a Claude Code session, run
/mcpand choose to authenticate. Claude Code opens your browser to sign in to Orbismo and choose which worlds this connection may access; tokens are then stored and refreshed for you. -
Ask Claude Code to list your worlds and switch to one, then start working. You can switch worlds anytime — see The connector.
By default the server is added for the current project. Use --scope user to make it available across all your projects, or --scope project to share it with your team via a checked-in .mcp.json.
A single world with an API key
Section titled “A single world with an API key”To pin Claude Code to one world, pass an API key as a header and use the world’s URL:
claude mcp add --transport http orbismo \ https://app.orbismo.com/api/v1/worlds/<world_id>/mcp \ --header "Authorization: Bearer oc_live_<your_key>"Replace <world_id> with your world’s UUID and oc_live_<your_key> with your full key. Use a read-only key first so the agent can’t make changes while you test.
Manage servers
Section titled “Manage servers”claude mcp list # show configured serversclaude mcp get orbismo # details for one serverclaude mcp remove orbismo # remove itVerify
Section titled “Verify”In a session, ask “What MCP tools do you have?” You should see Orbismo’s tools. On the connector, if none of the world tools appear, you probably don’t have a world active yet — ask Claude Code to list your worlds and switch to one. If something else is off, see Troubleshooting.