Connect an agent

Every agent uses the same address: https://api.joinarchon.com/api/mcp

Archon speaks the Model Context Protocol (MCP) over HTTPS and signs agents in with OAuth 2.1, so any client that supports remote MCP servers with sign-in works. The steps below cover the common ones.

1. You add the address to your agent.
2. The agent opens a page in your browser. If you are not signed in to Archon, you sign in first.
3. The page shows the agent's name and exactly what it asks for. You choose Approve or Deny.
4. The agent is now listed on the Agents page in your workspace, where you can limit, pause or disconnect it at any time.

The agent acts with your access and never more. If you cannot do something in Archon, neither can the agent you connected.

Claude Code

claude mcp add --transport http archon https://api.joinarchon.com/api/mcp

Then start Claude Code, run /mcp, choose archon and select Authenticate. Add --scope user to make Archon available in every project, or --scope project to share the address with your team through a .mcp.json file.

Cursor

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project), then open Cursor's MCP settings and choose Connect for Archon.

{
  "mcpServers": {
    "archon": {
      "url": "https://api.joinarchon.com/api/mcp"
    }
  }
}

VS Code

Run MCP: Add Server from the Command Palette and choose HTTP, or add this to .vscode/mcp.json. VS Code opens the browser the first time it connects.

{
  "servers": {
    "archon": {
      "type": "http",
      "url": "https://api.joinarchon.com/api/mcp"
    }
  }
}

Codex

codex mcp add archon --url https://api.joinarchon.com/api/mcp
codex mcp login archon

Or put this in ~/.codex/config.toml and run codex mcp login archon:

[mcp_servers.archon]
url = "https://api.joinarchon.com/api/mcp"

The command line

Not using an editor agent? Sign in with archon login and drive Archon from a shell or a script. See Command line.

Any other client

Point it at https://api.joinarchon.com/api/mcp as a remote (streamable HTTP) server. A client that supports MCP authorization finds the sign-in page by itself. See the reference for the discovery details.

• The agent says it was rejected (401) even though you never signed in. A fixed Authorization header in the agent's configuration turns browser sign-in off. Remove the header and connect again, or replace the token with a fresh one.
• The approval page does not open. Copy the address the agent prints and open it yourself. You must be signed in to Archon in that browser.
• The agent connects but cannot change anything. It was approved as read-only, or it is limited to some projects, or it is paused. Check it on the Agents page.
• You need an agent that cannot open a browser (a build server, for example). Create a token under Settings, API tokens, give it the fewest permissions it needs, and send it as Authorization: Bearer <token>. Treat it like a password.