Tailscale RMCP MCP server

tailscale-rmcp

Tailscale device, route, DNS, key, user, and ACL management over MCP and CLI.

It exposes one MCP tool, tailscale, plus the rtailscale CLI. Agents can list devices, inspect routes, read API keys, ACL policy, DNS settings, and users, authorize devices, and delete devices when the destructive gate is explicitly enabled.

30-second path: set TAILSCALEAPIKEY, then run npx -y @dinglebear/rtailscale devices --json -> start loopback HTTP with TAILSCALEMCPHOST=127.0.0.1 npx -y @dinglebear/rtailscale serve -> call tools/call with {"action":"devices"}.

Status: operational RMCP upstream-client server. Write-capable for device authorization; destructive device deletion requires both server opt-in and caller confirmation. HTTP MCP supports loopback dev mode, static bearer tokens, and Google OAuth through lab-auth.

Not for: replacing the Tailscale admin console, bypassing Tailscale account permissions, operating multiple unrelated tailnets from one trust boundary, storing API keys for callers, arbitrary WireGuard control, or passing Tailscale API keys through MCP tool arguments.

Contents

• Naming
• Capabilities And Boundaries
• Install
• Quickstart
• Client Configuration
• Runtime Surfaces
• MCP Tool Reference
• CLI Reference
• Configuration
• Authentication
• Safety And Trust Model
• Architecture

Naming

The repo, crate, and npm package use the RMCP family name. The shipped binary is rtailscale to avoid shadowing the official tailscale CLI.

Capabilities And Boundaries

ID.

• List devices and inspect a single device by node ID or legacy numeric device

users.

• Read subnet routes, API keys, ACL policy, DNS/MagicDNS settings, and tailnet

also passes explicit confirmation.

• Authorize a device for the tailnet.
• Delete a device only when TAILSCALEALLOWDESTRUCTIVE=true and the caller

• Provide setup and doctor commands for local plugin/runtime checks.

Install

Shortened. The full README is on GitHub.