Archee/Docs

Enter to open · Esc to close

Archee MCPView .md

Set up Archee MCP

Connect Claude Code, Codex, Cursor or Claude Desktop to Archee in about two minutes.

Fastest: tell your agent Set up Archee MCP for me by following https://docs.archee.studio/start/agent-setup.md and it does the steps below itself. See Let your agent set it up.

Server URL: https://mcp.archee.studio/mcp (Streamable HTTP). You need an Archee account on a plan that includes MCP; see Plans and credits.

Connect your client

  1. Add the server. Pick your client.

    # Claude Code
    claude mcp add --transport http --scope user archee https://mcp.archee.studio/mcp
    # Codex
    codex mcp add archee --url https://mcp.archee.studio/mcp
    // Cursor: ~/.cursor/mcp.json
    { "mcpServers": { "archee": { "url": "https://mcp.archee.studio/mcp" } } }
    Claude Desktop: Settings → Connectors → Add custom connector
    Name: Archee
    URL:  https://mcp.archee.studio/mcp
  2. Sign in. In Claude Code run /mcp and choose archee; in Codex run codex mcp login archee; other clients open the browser on first use. Sign in to Archee and approve the consent page; the client keeps and refreshes its own tokens.

  3. Check it. Ask your agent: “List the Archee calculations you can run.” It should call search and answer from the results.

Use a token instead

For CI, scripts or a client without browser sign-in, use a personal access token. Create one in the web app under Settings → Connected apps and tokens, then pass it as a bearer header:

# Claude Code
export ARCHEE_TOKEN=arch_pat_...
claude mcp add --transport http archee https://mcp.archee.studio/mcp \
  --header "Authorization: Bearer $ARCHEE_TOKEN"
# Codex: ~/.codex/config.toml
[mcp_servers.archee]
url = "https://mcp.archee.studio/mcp"
bearer_token_env_var = "ARCHEE_TOKEN"
// Cursor: ~/.cursor/mcp.json
{ "mcpServers": { "archee": {
  "url": "https://mcp.archee.studio/mcp",
  "headers": { "Authorization": "Bearer ${env:ARCHEE_TOKEN}" } } } }

Client configuration formats change. If one of these stops working, follow your client’s own remote-MCP documentation with the same URL and Authorization: Bearer header.

Disconnect

Revoke the connected app or the token under Settings → Connected apps and tokens. The next request from that client is refused. See Sign-in and tokens.

Next