Claude Desktop Integration

Connect Route6's MCP server to Claude Desktop to give Claude a real network identity — its own IPv6 address, web access from it, port forwarding and the team mesh.

Prerequisites

A Route6 API key (from the dashboard (opens in a new tab))
Claude Desktop installed
Node.js (for npx) — Claude Desktop's config file launches local servers, so an HTTP MCP endpoint is reached through the mcp-remote bridge

Config file location:

~/Library/Application Support/Claude/claude_desktop_config.json

Configuration

With the Route6 client (recommended)

Run the binary or the container first. It serves MCP on http://localhost:3000/mcp and already holds your key, so the config carries none:

{
  "mcpServers": {
    "route6": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://localhost:3000/mcp"]
    }
  }
}

Without a client (serverless)

Point the bridge at the gateway and pass your key as a header. Outbound tools only — no port forwards, webhooks or mesh:

{
  "mcpServers": {
    "route6": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://gw.route6.me/mcp",
               "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer sk_a6_your_key_here" }
    }
  }
}

Restart Claude Desktop after saving the config file.

Claude's Settings → Connectors also accepts a remote MCP URL, but it cannot send a Bearer header and runs from Anthropic's side, so it can reach neither localhost nor an API-key-authenticated endpoint. Use the config file.

Verifying the connection

In Claude Desktop, start a new conversation and ask:

"Use the route6 identity tool to tell me my public address and hostname."

Claude will call identity { action: "get" } and return your agent's IPv6 address, hostname and plan.

Available capabilities

Every plan, including Free, sees all 23 tools. After connecting, Claude can:

Fetch URLs from your agent's own address via web_fetch (IPv4 destinations work transparently via NAT64)
Check and rotate that address via identity
Ping, traceroute and resolve DNS with net
Search, browse and render pages (web_search, web_browse, web_fetch with render_js or screenshot — these use scraper credits)
Publish a local port or a webhook URL with port_forward (needs the client)
Coordinate with your other agents over the mesh with the team_* tools (needs the client)

Troubleshooting

The route6 server shows as failed: Check the client first: curl -s localhost:3001/status should report "transport": "connected". With the container, docker logs r6me shows why it could not connect. Then confirm npx -y mcp-remote http://localhost:3000/mcp starts in a terminal.

A tool returning upgrade_required: Every plan sees all 23 tools, so this is not a missing tool — it is one of the paid capabilities (your own hostname, scraper top-up, Static IPv4, outbound SMTP). The error names the tier and the next step. Upgrade at route6.me/dashboard/billing (opens in a new tab).

Scraper Pipe Cursor / Windsurf