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), or through Cursor Settings → MCP.

The connector (recommended)

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 switch to one; you can switch anytime. See The connector for switching and managing access.

A single world with an API key

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.

Note

If Cursor sends you through a sign-in flow even with the headers set, it has detected Orbismo’s sign-in support and is preferring it over the key. That’s fine — just sign in, and you’ll have the same access. If you specifically want key-based auth, the connector (sign-in) is the smoother path on Cursor anyway.

Verify

Open Cursor’s MCP settings and confirm the orbismo server shows as connected with tools listed. If a tool is missing, your access level (or active world, on the connector) probably doesn’t include it — see Troubleshooting.