Connect

Plug your AI tools into your brain.

One URL. OAuth-protected. Audited end-to-end. Connect once and every tool sees the same substrate, role-gated and policy-enforced.

Your connector URL is private.

Sign in to reveal the endpoint and copy it into your AI tools. The instructions below are the same for everyone; only the URL is per-customer.

Claude.ai

Web + mobile + desktop

Open Claude.ai → Settings → Connectors → Add custom connector.
Paste your connector URL (sign in to reveal). Claude.ai discovers the OAuth flow automatically.
Approve in the popup → connector lights up, tools become available in any chat.
Try: “Use atlasbrain to list my unpaid invoices.”

ChatGPT

Pro / Business / Enterprise

In ChatGPT settings, enable Developer mode (under Connectors or Beta features).
Connectors → Add custom MCP server → paste your connector URL.
Click Connect → approve in the OAuth popup → tools appear in the composer.
Try: “Use atlasbrain to search the substrate for ServiceStorm notes.”

Gemini CLI

Local · stdio

Install once: npm install -g @google/gemini-cli.
Add the server to ~/.gemini/settings.json (one-time config — see docs).
Run gemini → ask any question; the brain answers from your substrate.
Note: the Gemini consumer app/web does not yet accept remote MCP URLs the way Claude.ai and ChatGPT do. CLI is the supported path today.

Common questions

What does each AI tool see?

Only the rows your role allows, scoped to your tenant. Permissions are enforced once at the substrate boundary, not per-tool, so a new AI client inherits exactly the same view a new employee with the same role would get.

Is everything audited?

Yes — every tool call is hash-chained into a tamper-evident log with the calling user, the tool, the arguments, the policy decision, and the result digest. Same chain whether the call came from Claude, ChatGPT, the CLI, or a custom agent.

Does the URL change as I scale?

No. The URL is permanent. When a tenant promotes from the shared pool to a dedicated node, the routing is a database column change — your AI clients keep the same URL forever.

Where do tokens live?

In each AI client. We never see them after issuance — the OAuth flow runs through your browser. Revoke from the client (Claude.ai / ChatGPT) or contact us to rotate the signing key (kills all tokens at once).