Connect Claude Code (MCP)

Ian On can be reached from other AI tools. If you use Claude Code or another app that uses MCP (a common standard for connecting AI tools to data), you can let that tool search and ask your operating brain directly — without exporting files by hand. The connected tool can reach only what your account can see, and nothing more.

You don't need to be an admin. Any signed-in user can create their own key.

What the outside tool can do

Once connected, the tool gets four abilities, all limited to what your account is allowed to access.

• Search your company knowledge (ian_search).
• Ask for a grounded answer with sources (ian_ask). If the request should be handled as work, it doesn't answer and instead tells you to create the work with ian_work_create.
• Look up decisions (ian_decision_query) — pick one piece of work and see, from that work's decision ledger, who decided what, why, and when.
• Start work from a goal (ian_work_create) — it creates your personal work, starts planning it, and returns a link to that work.

A decision lookup must name the work to look up: pass its id (a UUID) as workspaceId. The id is the <id> part of the work page address /work/<id>. Whatever your role, it looks up one piece of work at a time. You can look up team work only while you currently belong to that team, and personal work only if you created it.

An ian_work_create request can optionally carry an ian-on/logical-action-id value in the request's _meta. The value is 1 to 200 characters made of English letters, digits, and . _ : -; a value in any other form comes back with an error. When you retry the same request, send the same value and you get the same work back; without a value, every call creates new work.

Setting it up

1. Open Settings → MCP API keys.
2. Optionally enter a key name (for example, Claude Code) and click Create.
3. The key is shown only once — copy it now with Copy and keep it safe. You can't see it again.
4. The page also shows a ready-to-paste config. Put it in your tool's .mcp.json:

{
  "mcpServers": {
    "ian-on": {
      "type": "http",
      "url": "https://<your-ian-on>/api/mcp",
      "headers": { "Authorization": "Bearer <your-key>" }
    }
  }
}

Restart your client and check that the four tools appear. Ian On provides only tools, so empty resource and prompt lists are normal. For each tool's inputs and how to fix errors, see Settings → MCP API keys → Connection guide in the app.

To revoke access, click Revoke next to the key in the same section, then confirm once more in the dialog. Revoking can't be undone, and any outside tool that was using that key loses access right away.