Cloud MCP authentication

MCP API Keys

Long-lived credentials for the ArchRails cloud MCP server. Generate a key, then follow the Wire up your IDE steps below for Claude Code, Cursor, Windsurf, or any MCP-compatible client. One active key per developer; minting a new key auto-revokes the previous one. Default lifetime: 30 days.

Loading your account…

Signed in as

Tenant:

Mint a new key

The raw key value is shown once, then only its hash is stored. Save it to your IDE config immediately. Devs: you can mint for yourself only. Maintainers / admins: you can mint for any user in this tenant.

Cognito username (optional)

Devs: leave blank. Admins/maintainers: target email/sub.

Expiry (days)

Wire up your IDE

✓ Key minted. Use it in the archrails login --paste step below — the CLI caches it in ~/.archrails/credentials.json (mode 0600) so the MCP server can authenticate.

Pick your editor below. Each path runs the same archrails CLI as a stdio MCP server. Already cached a key? Skip the archrails login --paste step.

1Install the CLI

One-time. Requires Python 3.10+.

pip install archrails-mcp

2Run bootstrap

Auto-installs Node.js + the FINOS CALM CLI, opens a browser to sign you in (no copy/paste), wires ~/.claude.json for Claude Code, and runs a smoke check.

archrails bootstrap

3Restart your editor

For Cursor/Windsurf/VS Code, also follow the IDE-specific tab to register the MCP server in that client's config.

1Install the CLI

pip install archrails-mcp

2Cache your API key

Paste the key shown above when prompted. Input is hidden. Stored at ~/.archrails/credentials.json (mode 0600).

archrails login --paste

3Register the MCP server

Adds an entry under mcpServers in ~/.claude.json via the Claude Code CLI.

claude mcp add archrails -- archrails mcp start --repo .

4Restart Claude Code

Verify with /mcp — you should see archrails with 4 tools (get_architecture_context, check_proposed_change, scan_repo_for_drift, list_owned_repos).

1Install the CLI

pip install archrails-mcp

2Cache your API key

archrails login --paste

3Add ArchRails to Cursor's MCP config

File: ~/.cursor/mcp.json — create it if missing. If you already have mcpServers entries, merge into the existing object.

{
  "mcpServers": {
    "archrails": {
      "command": "archrails",
      "args": ["mcp", "start", "--repo", "."]
    }
  }
}

4Restart Cursor

Open Cursor Settings → MCP. archrails should appear with a green status dot. Test in chat: "Use the archrails MCP server to call get_architecture_context."

1Install the CLI

pip install archrails-mcp

2Cache your API key

archrails login --paste

3Add ArchRails to Windsurf's MCP config

File: ~/.codeium/windsurf/mcp_config.json — create it if missing.

{
  "mcpServers": {
    "archrails": {
      "command": "archrails",
      "args": ["mcp", "start", "--repo", "."]
    }
  }
}

4Restart Windsurf

Cascade → Settings → MCP servers. Confirm archrails is listed and refresh tools.

1Install the CLI

pip install archrails-mcp

2Cache your API key

archrails login --paste

3Add ArchRails to Continue's config

File: ~/.continue/config.yaml — append to mcpServers.

mcpServers:
  - name: archrails
    command: archrails
    args: ["mcp", "start", "--repo", "."]

4Reload VS Code

Command Palette → Developer: Reload Window. Continue's tool drawer should list archrails's 4 tools.

1Install the CLI

pip install archrails-mcp

2Cache your API key

archrails login --paste

3Point your MCP client at archrails

Generic stdio MCP server stanza — works with any MCP-compatible client (Zed, custom agents, MCP inspector). The CLI reads credentials from ~/.archrails/credentials.json; no env vars needed.

{
  "command": "archrails",
  "args": ["mcp", "start", "--repo", "."],
  "env": {}
}

4Smoke-test from a terminal

If your client doesn't surface errors well, run the server directly and send a tool list request via the MCP inspector or stdio JSON-RPC.

archrails mcp start --repo .

MCP API Keys

Your account isn't provisioned for ArchRails yet

Mint a new key

Wire up your IDE

Your keys