Connect an AI tool

Orbismo exposes every world through the Model Context Protocol (MCP). Any MCP-aware AI tool — Claude, ChatGPT, Cursor, custom agents — can connect to your world, see the same entities and lore your team browses in the portal, and, depending on permissions, make changes that show up in the portal as soon as you refresh. Connecting an AI tool is also how you create and edit your world’s content.

Pick your tool

ClaudeOne click — Orbismo is in the Claude Connectors Directory. Works on web and desktop.

Claude CodeOne claude mcp add command in the CLI, then sign in.

ChatGPT / OpenAIInstall the Orbismo plugin from the ChatGPT plugin directory.

CursorAdd the connector as an MCP server and sign in.

OpenClawPoint OpenClaw at one world with an API key.

Other MCP clientsAny MCP-aware tool — including stdio-only clients via a bridge.

If a connection isn’t working, start with Troubleshooting.

The mental model

A world is one canon with two ways in:

• The MCP server — where content gets authored: AI agents you direct create, edit, and link entities and lore.
• The web portal — where your team browses the canon and manages the world, its settings, and its collaborators.

Both look at the same data. World content in the portal is read-only today — the MCP server is where changes happen — and whatever your agent creates is visible in the portal on refresh.

How a connection works

Every setup guide above uses one of two connection styles:

• The connector (most people) — one URL for every world you grant, using sign-in with Orbismo (OAuth). The tool stays connected while the agent switches between worlds on the fly. In Claude there’s no URL to paste at all — Orbismo is in the Claude Connectors Directory. See The connector for how switching and access work.

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

• A world URL — points a tool at a single world, fixed in the address. Sign in, or — for scripts and bearer-only tools that can’t do a sign-in flow — use a per-world API key (oc_live_…).

  https://app.orbismo.com/api/v1/worlds/{world_id}/mcp

Note

The connector needs a client that supports MCP sign-in (OAuth). API keys only work on a world URL. Signing in works with both.

You’ll find both URLs in the portal: a world’s URL under World Settings → API Connections, and the connector URL on the Connected AI and Apps page.

Both endpoints speak Streamable HTTP — the modern MCP transport, supported natively by most MCP clients. For clients that only speak stdio, see Other MCP clients for the bridge pattern.

Permissions

What a connected tool can do is governed by your role on each world:

• Read-only access — the agent can query, search, and read lore but can’t make changes.
• Read-write access — the agent can create, update, and delete entities, lore, and relationships.

With an API key, you set the key’s permission when you create it (a viewer can only create read-only keys). When you sign in, the agent acts with your role on whichever world is active — and on the connector, only worlds in the app’s grant are reachable at all. Either way, the agent only sees the tools its permission allows — if a tool is missing, the connection probably doesn’t have the permission for it.

Try these prompts

Once you’re connected, paste any of these into your AI tool. The agent figures out which MCP tools to call — you just describe what you want in your world’s vocabulary. Read-only prompts work with any connection; the ones that create or link entities need read-write access.

Being connected isn’t the same as being used

Claude and ChatGPT don’t load every connected tool in every chat. The reliable way to invoke Orbismo is to name it — start your prompt with “Connect to Orbismo and …” (in ChatGPT, also select Orbismo from the composer’s + menu first). Each setup guide covers the details for its tool.

Get oriented in an unfamiliar world.

Give me a full briefing on the entity "Maria Santos" — relationships, lore, and any connected entities I should know about.

Trace a connection you’d forgotten about.

Find every person who is a member of the group "Northside Book Club", and tell me which of them have attended the same events together.

Spot the gaps.

What entities in this world don't have any lore attached yet? Group them by entity type so I can see where I should focus.

Catch contradictions.

Look for chronological conflicts in this world — someone in two places at once, events out of sequence, or dates that don't add up.

Build from a draft.

I just sketched three new places in this note: <paste your text>. Create them as place entities, link each one to the group that meets there, and tag any that are outdoors.

Turn prose into a graph.

Read the lore attached to "Summer Reunion 2025" and create relationships between every person and group mentioned in it.

Next steps

• World instructions — teach your AI how your world works once it’s connected.
• The connector — switching worlds and managing which apps reach what.
• Generate an API key — for scripts and bearer-only tools.