Lite Client Quick Start

The simplest way to give your agent a Route6 identity. Works anywhere — your laptop, serverless functions, CI/CD, cloud VMs. No Docker, no root, no kernel modules.

The Lite client talks to the hosted gateway at gw.route6.me. Lite and Pro (Docker) are connection methods, not tiers — any plan can use either, and you can switch any time.

Install

npm install -g @route6/agent
# or
pip install route6

Both packages install the same route6 command.

Log in

route6 login sk_a6_your_key_here

This saves your API key to ~/.route6/config.json (mode 0600) and verifies it against the gateway.

Connect via MCP

You have two options:

Option A — local MCP proxy (works with editors that expect a localhost URL):

route6 mcp serve --port 3000

Point your MCP client at http://127.0.0.1:3000/mcp. The proxy forwards every call to https://gw.route6.me/mcp with your API key as a Bearer token — same config as the Docker container.

Option B — point your client straight at the gateway (no local process):

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

All 27 MCP tools are available through the gateway — same tools, same API, same results as the Docker container (subject to your plan tier).

Expose a local service to the internet

The Lite client can tunnel a local port out to a public *.on.route6.me hostname — no router config, no Docker:

route6 tunnel start --hostname my-app --to 3000

Your service is now reachable at https://my-app.on.route6.me/. Repeat --hostname/--to for multiple services.

When to use Pro (Docker) instead

Run the route6me/netid container if you need:

• Raw TCP/UDP port forwarding — Lite inbound is HTTPS (port 443) only; the container forwards any TCP/UDP port.
• Direct mesh networking between agents over the WireGuard fabric.
• Container-local tool execution — net_ping, net_traceroute, and web_fetch run on your host rather than being proxied through the gateway.