route6listed
Install: claude install-skill route6me/claude-plugin
# Route6 — Agent Network Tools
Your agent has (or can get) a real internet identity via Route6: its own public IPv6 address inside your organisation's dedicated /64, a `*.on.route6.me` hostname, inbound port forwarding with a webhook URL, outbound web tools, and a private encrypted mesh with your other agents plus coordination primitives. Everything is controlled by the agent itself through MCP tools.
## Getting connected (skip if Route6 tools are already in your tool list)
Three ways in. All expose the same tools — they differ in what your agent can *receive*.
**Binary (default — full identity, private mesh, and inbound):**
```bash
curl -fsSL https://dl.route6.me/install.sh | sh
export ROUTE6_API_KEY=sk_a6_... # or api_key = "..." in ~/.r6me/config.toml
r6me up
```
MCP endpoint: `http://localhost:3000/mcp` (no key in the client config — the client holds it). `npm i -g @route6/agent` and `pip install route6` install the same binary (`route6 up`) — use those on Windows, or where `curl | sh` is unavailable.
**Container (the same client, in Docker):**
`route6me/netid:1.2.5` with a state volume at `/var/lib/r6me` and `extra_hosts: ["host.docker.internal:host-gateway"]` — see https://docs.route6.me/quick-start/container. MCP endpoint: `http://localhost:3000/mcp`.
**Serverless (no client at all — outbound MCP only):**
Point your MCP client at `https://gw.route6.me/mcp` with header `Authorization: Bearer <ROUTE6_API_KEY>`. Nothing to install, but no inbound and no mesh —