Skip to content

Cursor

Cursor supports remote MCP servers over Streamable HTTP, so it connects to Orbismo directly. Configure it in ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project — this wins if both define the same server), or through Cursor Settings → Tools & MCP.

Point Cursor at the connector URL and let it sign you in:

{
"mcpServers": {
"orbismo": {
"url": "https://app.orbismo.com/api/v1/mcp"
}
}
}

When Cursor loads the server it runs an Orbismo sign-in flow in your browser, where you choose which worlds this connection may access. After that, ask Cursor’s agent to list your worlds and tell it which one to work in; you can move to another anytime. See The connector for choosing a world and managing access.

To pin Cursor to one world, use the world’s URL and pass an API key in a headers block:

{
"mcpServers": {
"orbismo": {
"url": "https://app.orbismo.com/api/v1/worlds/<world_id>/mcp",
"headers": {
"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.

Open Cursor Settings → Tools & MCP and confirm the orbismo server shows as connected with its tools listed. On a single-world URL, a missing tool usually means your access level doesn’t include it. On the connector the tool list is the same for every world. On a read-write connection, write tools stay listed even on worlds where you are a viewer, and the change is refused when the agent tries it. Cursor also caps the total number of tools across all your MCP servers at 40 — if you run several servers at once, some of Orbismo’s tools can silently drop out, so disable servers you aren’t using. See Troubleshooting.