Tailscale RMCP

Rust MCP server and CLI for Tailscale devices, users, keys, policies, and auth.

Tailscale RMCP is a Rust-implemented MCP server and CLI that exposes Tailscale network management operations to AI agents and MCP-compatible clients. It targets the core administrative surface of a Tailscale network: devices, users, auth keys, access control policies, and authentication flows. The server is distributed as an npm package (version 0.1.3) under the publisher ai.dinglebear and communicates over the stdio transport, which means the agent process spawns it as a subprocess and exchanges MCP messages through standard input and output.

Configuration is handled entirely through environment variables. TAILSCALE_API_KEY supplies the credentials used to authenticate against the Tailscale API. TAILSCALE_RMCP_VERSION, TAILSCALE_RMCP_REPO, and TAILSCALE_RMCP_RELEASE_BASE_URL control which binary release is fetched. RUST_LOG enables log-level tuning for debugging.

Because no tool definitions are currently published in the registry record, the exact set of agent-callable operations cannot be enumerated here. The stated scope — devices, users, keys, policies, and auth — indicates the intended domain coverage, but developers should consult the source repository at github.com/jmagar/tailscale-rmcp to confirm which endpoints are implemented in this release. This server is suited for automating Tailscale administration tasks inside an agentic workflow, but it is not a general networking or VPN configuration tool beyond the Tailscale API surface.

Use cases

  • Automate Tailscale device inventory queries inside an AI agent workflow
  • Manage Tailscale auth key lifecycle (creation, revocation) through an MCP client
  • Apply or audit Tailscale ACL policies programmatically via an agent
  • Administer Tailscale user accounts as part of an onboarding automation pipeline

When to use it

  • When an AI agent needs to query or manage a Tailscale network without direct API integration
  • When the runtime environment supports stdio-transport MCP servers
  • When Tailscale API key credentials can be securely supplied as environment variables

When not to use it

  • When the agent runtime requires HTTP or SSE transport rather than stdio
  • When managing VPNs or network infrastructure outside of Tailscale
  • When a stable, production-hardened tool list is required — this is version 0.1.3 with no tool definitions confirmed in the registry
  • When no license information is acceptable in a compliance-controlled environment — no license is recorded for this package