Claude Code

Claude Code — Anthropic’s terminal CLI — registers Aurora MCP with a single command. The CLI handles OAuth using your default browser, then resumes automatically once authorisation completes.

Prerequisites

• Claude Code installed and authenticated (claude --version prints a version).
• A Consilio account that can sign in at auth.ai.consilio.com.
• Outbound HTTPS to mcp.ai.consilio.com and auth.ai.consilio.com.

Add the connector

From any shell:

claude mcp add consilio https://mcp.ai.consilio.com

By default the connector is registered at user scope, meaning it’s available across all your Claude Code sessions on this machine. Pass --scope project to scope it to a single project (writes to .claude/mcp_servers.json in the current repo) or --scope local for session-only.

Verify the registration:

claude mcp list

You should see:

consilio  https://mcp.ai.consilio.com  (remote, oauth)

One URL is all you need

You don’t pass a client ID, secret, or scope list. Claude Code reads https://mcp.ai.consilio.com/.well-known/oauth-protected-resource and discovers the rest.

Authorise

The first time you invoke an Aurora MCP tool inside a session, Claude Code opens your default browser to auth.ai.consilio.com. Sign in as yourself, approve the consent screen, and the browser tab closes itself. The CLI resumes the prompt as soon as the handshake completes.

Verify

Inside any Claude Code session, try:

List workspaces for matter A12345.

Claude Code invokes searchWorkspaces, displays the tool-call summary, and renders the results inline. You can also try:

What active matters do I have for Coho Capital?

— maps to searchMatters, no alpha-code required.

Removing or refreshing the connector

# Remove
claude mcp remove consilio

# Refresh OAuth (forces re-auth on next call)
claude mcp logout consilio

Troubleshooting

claude mcp add says “command not found”

Your Claude Code CLI is older than the Remote MCP feature. Update it (npm install -g @anthropic-ai/claude-code or your equivalent install path).

The browser tab opens but the CLI never resumes

Claude Code is waiting on a localhost callback. Check that nothing is intercepting 127.0.0.1 traffic (corporate VPNs occasionally do this). If you’re SSH’d into a remote machine, you’ll need to forward the callback port — see the Remote-host workflow below.

”401 Unauthorized” inside a session

Token expired or audience binding rejected the request. Force a re-auth:

claude mcp logout consilio

Then invoke any Aurora MCP tool; the OAuth tab opens again.

Tool calls succeed in one project but fail in another

You probably installed Aurora MCP at --scope project in the working project but not the other. Either reinstall there, or move the registration to user scope:

claude mcp remove consilio
claude mcp add consilio https://mcp.ai.consilio.com   # defaults to --scope user

Remote-host workflow (SSH, devcontainer)

If you’re running Claude Code on a remote machine, the OAuth browser needs to open on your local machine but redirect back to the remote. Forward the local callback over SSH:

ssh -L 8765:localhost:8765 your.host.example.com

Then on the remote shell:

BROWSER=none claude mcp add consilio https://mcp.ai.consilio.com

Claude Code prints the auth URL; copy it into your local browser, sign in, and the SSH tunnel returns the redirect to the CLI.

What’s next

• Try Claude Desktop for a GUI on the same account.
• Read the Security model — gateway-side token validation, identity-header injection.
• See the FAQ for support contacts and SLA.