Connect Claude

Connect Claude to Archie

Add one URL in Claude, Cursor, VS Code, or Cowork. Your conversations gain 72 tools backed by your firm's real data and the full orchestrator. No API key to manage. Archie does the work the moment the client connects.

The connect URL

https://mcp.dev.arch.ie/mcp

Add It to Your Client

Each client takes the URL a little differently. Pick yours, copy the snippet, and sign in with your firm's SSO. Claude Desktop connects from its own settings, not a config file.

terminal

claude mcp add --transport http archie https://mcp.dev.arch.ie/mcp

# then, in a session:
/mcp

Prove it works by asking “List my Archie clients”. That calls list_clients and confirms the token round-trip and the access layer are healthy.

Connect Archie to Cowork

Cowork takes the same connector, then adds Archie's plugin on top for slash commands and the know-how to use them. Six steps from a blank canvas to a live artifact.

In Cowork: Settings → Connectors → Add custom connector. Paste https://claude.dev.arch.ie/mcp. The /mcp ending matters.
Cowork finds Archie's sign-in on its own and opens your browser. Sign in with your firm's SSO and pick your workspace. Archie mints a short-lived workspace key, so he only ever sees what you can see.
Prove he is there: ask “List my Archie clients.” He calls list_clients and answers from your real ledger.
Install the Archie plugin to get slash commands and the know-how: Customize → Browse plugins → Upload custom plugin, select the archie folder, sign in once more.
Run /archie:meeting-prep and watch a live artifact panel render in the canvas. Draft a playbook with /archie:playbook-new; when Archie wants to write, he pauses for your approval in the canvas.
When your 15-minute key expires, Cowork signs you back in with one click. Manage or revoke a connection from Connections.

The plugin bundles the connector, three skills, four slash commands, and four sub-agents. Its full contents and changelog live alongside the code at plugins/archie-cowork.

What You Grant

On first connect you grant four scopes. Every call still passes through your workspace permissions, so a user who cannot see a client in the web app cannot see them through Claude either.

read:accountingRead-only

Standards research, knowledge-base search, document analysis, and read-only advisory.

read:clientsRead-only

List clients and read the financials and payroll the user already sees in the web app.

write:journalsWrite

Post journals, reconcile, and classify transactions. Amounts above the auto-approval threshold pause for a human.

write:communicationsWrite

Draft client emails, letters, memos, and reports. Every draft lands in the queue, never sends silently.

See the full scope-to-tool mapping in the tool catalog, and how writes pause for a human in the confirmation contract.

When Something Is Off

Empty tool list after connecting

Most often the OAuth flow closed before the workspace picker. Revoke from Connections, reconnect, and pick a workspace. Second cause: a stale Claude Desktop cache. Quit it fully and reopen.

401 on every call

The bearer resolver only accepts tokens whose issuer matches this tier's connector URL. Reconnecting almost always fixes it.

403 on a write tool

Either the workspace permission is missing (grant it from Team) or the token was minted before the user granted write:journals. Reconnect to upgrade the scope.

Discovery endpoints, token shape, and how the Host header drives the issuer live on the MCP protocol spec.