Other MCP clients

Any MCP-aware tool can connect to Orbismo. The details are the same everywhere — only how you enter them differs by client. Pick the method your client supports.

The connector (sign-in)

If your client supports MCP sign-in (OAuth) connectors, point it at the connector URL:

https://app.orbismo.com/api/v1/mcp

The client sends you to Orbismo to sign in and choose which worlds it may access, then the agent can switch between them. No key to store.

A single world with an API key

If your client authenticates with a bearer token / custom header, use a world’s URL and an API key:

• Transport: Streamable HTTP
• URL: https://app.orbismo.com/api/v1/worlds/<world_id>/mcp
• Auth header: Authorization: Bearer oc_live_<your_key>

This pins the client to that one world. Use a separate key per world.

stdio-only clients

Some clients only speak the older stdio MCP transport and can’t open an HTTP URL directly. Bridge them with mcp-remote (needs Node.js 18+), which wraps a remote HTTP server as a stdio one:

npx -y mcp-remote https://app.orbismo.com/api/v1/worlds/<world_id>/mcp \
  --header "Authorization: Bearer oc_live_<your_key>"

Most clients let you set a command and args for a stdio server — use npx with the arguments above. The Claude Desktop guide shows this pattern in a full config file.

Still stuck?

See How AI integration works for the full connection model, or Troubleshooting for common errors.