Claude

This guide connects Claude (Desktop or web) to Orbismo over MCP. Once connected, Claude can read your entities and lore, search your world, and — with write access — create and edit content that shows up in the portal when you refresh.

There are two ways to connect:

• The connector (recommended) — Orbismo is listed in the Claude Connectors Directory. Connect it with a click, sign in with Orbismo, and Claude can reach every world you grant it and switch between them in conversation. No URL to paste, no custom connector to configure.
• A single world with an API key — pin Claude to one world using the mcp-remote bridge.

Connector (recommended)

1. Open Orbismo in the Claude Connectors Directory and click Connect. (You can also find Orbismo from inside Claude: Settings → Connectors → Browse connectors.)

2. Claude opens Orbismo in your browser to sign in and choose which worlds this connector may access. Approve, and you’re returned to Claude.

3. Start a new chat and ask “what tools do you have?” — you should see Orbismo’s tools. If no world is active yet, ask Claude to list your worlds and switch to one.

Note

Because Orbismo is in the directory, there’s nothing to configure by hand — no custom connector, no URL. The connector is signed-in access — there’s no key to copy or rotate, and you manage which worlds it can reach (or revoke it) from the portal’s Connected AI and Apps page. See The connector.

Single world (API key)

Claude Desktop’s connector UI doesn’t accept a static token, so to pin Claude to one world with an API key you use mcp-remote, which bridges a remote HTTP MCP server to the stdio transport Claude Desktop expects. It runs npx mcp-remote … under the hood, so you’ll need Node.js 18+ installed.

You’ll need your world’s ID (the UUID in the portal URL when you’re inside a world) and an API key for that world. Use a read-only key for your first connection so Claude can’t change anything while you test.

1. Open Claude Desktop’s config file:

   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json

   Create it if it doesn’t exist.

2. Add an orbismo entry under mcpServers (merge into any existing servers — don’t replace them):

   {
     "mcpServers": {
       "orbismo": {
         "command": "npx",
         "args": [
           "-y",
           "mcp-remote",
           "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.

3. Fully quit Claude Desktop (on macOS, ⌘Q — closing the window isn’t enough), then reopen it.

4. Start a new chat and ask “What MCP tools do you have access to?” You should see tools like search_entities and get_world_context. If not, see Troubleshooting.

To connect more than one world this way, add a separate entry per world (orbismo-world-a, orbismo-world-b, …), each with its own world URL and API key. Keys are scoped to a single world. (Or use the connector, which handles multiple worlds with no extra config.)

Getting Claude to use Orbismo

Connecting Orbismo doesn’t mean Claude uses it in every chat. By default, Claude’s tool access is set to Auto — it decides which connectors to load based on what you’re asking about. If your prompt doesn’t obviously involve your world, Claude may answer from its own knowledge and never touch Orbismo.

The reliable fix: name Orbismo at the start of your prompt.

Connect to Orbismo and give me a full briefing on "Maria Santos" — relationships, lore, everything.

If you have several worlds, name the world too:

Connect to Orbismo, switch to my "Family History" world, and list the people I added most recently.

You can also manage this by hand in any chat: click the + button in the message box (or type /), hover Connectors, and toggle Orbismo on for that conversation. The same menu’s Tool access setting controls the loading behavior (Auto, Always available, or On demand) if you’d rather Orbismo always be ready.

Once Claude is using Orbismo, talk to your world directly — Claude picks the right tool for each request:

• “Search this world for anyone connected to the Northside Book Club.”
• “Create a place called ‘Riverside Café’ and link it as a spot the group ‘Northside Book Club’ meets at.” (write access required)
• “Switch to my Family History world.” (connector only — moves between worlds mid-conversation)

Skip the preamble with a skill

If every session starts the same way — connect to Orbismo, load the same world — wrap that preamble in a custom Claude skill. A skill is a small instruction file Claude applies automatically whenever a request matches its description, so “add a journal entry about today’s hike” just works — no “Connect to Orbismo and…” required.

Anthropic’s help center covers how to create and upload a skill; all Orbismo needs from yours is a SKILL.md like this:

---
name: personal-journal
description: Journaling in my Orbismo "Personal Journal" world. Use for any request about my journal — adding entries, or recalling people, places, and events from my life.
---

Connect to Orbismo and switch to the "Personal Journal" world.
Confirm the world is active, then use Orbismo's tools to carry out the request.

Tip

The description (200 characters max) is what triggers the skill — Claude matches it against each request. Describe the tasks it covers (“adding entries, recalling people and events”), not just the world’s name. One skill per world works well if you keep several.

Pair the skill with world instructions — the skill gets Claude into the right world; world instructions tell it how to behave once there (see the journaling example).

Next steps

• The connector — switching worlds and managing access.
• Generate an API key — for the single-world method.
• Troubleshooting if something isn’t working.