Claude Desktop Integration

Connect Route6's MCP server to Claude Desktop to give your Claude agent full network capabilities — IPv6 identity, web access, mesh networking, and more.

Prerequisites

A Route6 API key (from the dashboard (opens in a new tab))
Claude Desktop installed
For Pro: the route6me/netid container running. For Lite: nothing else — it's serverless.

Config file location:

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

Configuration

Pick a connection method — both expose the same MCP surface.

Lite (recommended — no Docker)

Point Claude Desktop straight at the hosted gateway with your API key as a Bearer token:

{
  "mcpServers": {
    "route6": {
      "url": "https://gw.route6.me/mcp",
      "headers": { "Authorization": "Bearer sk_a6_your_key_here" }
    }
  }
}

(Or run route6 mcp serve --port 3000 from the Lite client and use http://localhost:3000/mcp.)

Pro (Docker)

With the container running (docker compose up -d, MCP bound to 127.0.0.1:3000):

{
  "mcpServers": {
    "route6": {
      "type": "http",
      "url": "http://localhost:3000/mcp"
    }
  }
}

Restart Claude Desktop after saving the config file.

Verifying the connection

In Claude Desktop, start a new conversation and ask:

"Use the identity_get tool to tell me what Route6 agent I'm connected to."

Claude will call identity_get and return your agent's IPv6 address, hostname, and tier.

Available capabilities

After connecting, Claude can:

Fetch URLs from any site via web_fetch (IPv4 destinations work transparently via NAT64)
Check and rotate your public IPv6 address via identity_set_ipv6 (omit address to rotate)
Ping, traceroute, and resolve DNS
(Paid tier) Search the web, take screenshots, browse JS-rendered pages
(Paid tier) Set a custom hostname, create port forwards
(Paid tier) Join a private mesh and communicate with other agents

Troubleshooting

"MCP server not found" error: Run docker ps | grep route6-agent — if empty, the container isn't running. Check docker logs route6-agent for startup errors.

"Tool call failed: tunnel not up": Check docker logs route6-agent | grep WireGuard — the tunnel may have failed to initialize. Common cause: missing --cap-add NET_ADMIN. Re-create the container with that flag.

Tools returning "tier restricted": Free tier has 7 tools. Upgrade at route6.me/dashboard/billing (opens in a new tab).

Scraper Pipe Cursor / Windsurf