mcpdirectory.dev
9,129 servers · updated 23 Sept

Rtailscale MCP server

community Active last commit 29 d
{
  "mcpServers": {
    "dinglebear-rtailscale": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/rtailscale@latest"
      ],
      "env": {
        "TAILSCALE_RMCP_RELEASE_BASE_URL": "https://...",
        "TAILSCALE_API_KEY": "<tailscale_api_key>",
        "TAILSCALE_MCP_TOKEN": "<tailscale_mcp_token>",
        "TAILSCALE_MCP_PUBLIC_URL": "https://...",
        "TAILSCALE_MCP_GOOGLE_CLIENT_ID": "<tailscale_mcp_google_client_id>",
        "TAILSCALE_MCP_GOOGLE_CLIENT_SECRET": "<tailscale_mcp_google_client_secret>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @dinglebear/rtailscaleversion 0.1.4

What it does

MCP server for reading and managing Tailscale devices, routes, DNS settings, API keys, users, and ACLs. Exposes a `tailscale` MCP tool and `rtailscale` CLI. Designed for developers and AI agents that need to inspect or administer Tailscale networks.

  • List all devices in a tailnet and inspect details for a specific device by node ID.
  • Read and manage DNS settings, subnet routes, and ACL policy for a Tailscale network.
  • Authorize new devices to join a tailnet or delete devices when destructive operations are explicitly enabled.

Tools this server exposes

ToolDoes
tailscaleExposes Tailscale management operations including device listing, authorization, deletion, and inspection of routes, DNS, ACLs, and API keys.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.