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
- Docker installed and running
- Route6 container running (
docker ps | grep route6-agent) - Claude Desktop installed
Configuration
Add the Route6 MCP server to your Claude Desktop config:
Config file: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"route6": {
"command": "docker",
"args": [
"exec", "-i", "route6-agent",
"node", "/app/mcp-server.js"
]
}
}
}Restart Claude Desktop after saving the config file.
Make sure your container is named route6-agent (the name used in docker run --name route6-agent ...).
If you used a different name, update the args accordingly.
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 IPv6-reachable site via
web_fetch - 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 11 tools. Upgrade at route6.me/dashboard/billing (opens in a new tab).