Tailscale RMCP (dinglebear-ai)

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.

People who work with automation, claude code plugins and codex and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in Rust.

VERIFIED ACTIVE

LAST COMMIT 2026-08-25 · ★ 5 · #117 OF 227 MAINTAINED AUTOMATION · VERIFIED 2026-09-18

AGPL-3.0 · Rust servers · how we verify → /methodology

01 · Install Tailscale RMCP (dinglebear-ai)

before you install - you'll need

Set TAILSCALE_API_KEY, TAILSCALE_TAILNET, TAILSCALE_MCP_HOST before connecting.

Claude Code

claude mcp add dinglebear-ai-rtailscale --transport http https://ts.dinglebear.ai/mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "dinglebear-ai-rtailscale": {
      "url": "https://ts.dinglebear.ai/mcp"
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

https://ts.dinglebear.ai/mcp

transport: streamable-http

endpoint NOT responding · probed 2026-09-18

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions · remote - your agent's requests go to ts.dinglebear.ai

license AGPL-3.0 - declared in the repository

npm package @dinglebear/rtailscale - the @dinglebear scope differs from the repo owner (dinglebear-ai); confirm it's the project's official package

registry vendor namespace ai.dinglebear - domain-verified with the official MCP registry

03 · What Tailscale RMCP (dinglebear-ai) can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v0.1.4 · 2026-07-28

0.1.4 (2026-07-28) · Fixed · run canonical rtailscale container binary

v0.1.3 · 2026-07-13

0.1.3 (2026-07-13) · Fixed · harden package release checks · route rust builds through sccache wrapper

v0.1.2 · 2026-07-09

Sync npm package README with the repository README so npmjs shows the full docs.

04 · Who maintains Tailscale RMCP (dinglebear-ai)

Tailscale RMCP is maintained by dinglebear-ai. We track 11 MCP servers from dinglebear-ai - 11 actively maintained, 42 combined GitHub stars, oldest repo from Mar 2026. Full record: all servers from dinglebear-ai.

  1. Cortex RMCP Self-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS. ★ 3
  2. Labby Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI. ★ 6
  3. Yarr MCP Self-hosted media fleet operations across Sonarr, Radarr, Plex, and related apps over MCP and CLI. ★ 12
  4. Apprise RMCP Apprise notifications over MCP and CLI with authenticated stdio and HTTP transports. ★ 2
  5. YTDL RMCP yt-dlp search, download, metadata, delivery, and Plex workflows over MCP and CLI. ★ 2
  6. Gotify RMCP Gotify notifications and app, client, and message management over MCP and CLI. ★ 2

05 · Facts

category
automation - ranked #117 of 227 actively-maintained automation servers as of 2026-09-18.
release cadence
4 releases in the last 90 days (latest 2026-07-28)
registry
ai.dinglebear/rtailscale (active, first published 2026-08-04)
packages
npm:@dinglebear/rtailscale

06 · Tailscale RMCP (dinglebear-ai) FAQ

What is Tailscale RMCP (dinglebear-ai)?

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.

Is Tailscale RMCP (dinglebear-ai) still maintained?

Yes - as of 2026-09-18, its last commit was 2026-08-25 and it shipped 4 releases in the last 90 days. We re-verify nightly.

How do I install Tailscale RMCP (dinglebear-ai)?

Run `npx -y @dinglebear/rtailscale`. The README documents 3 environment variables (TAILSCALE_API_KEY, TAILSCALE_TAILNET, TAILSCALE_MCP_HOST) to set first. Set TAILSCALE_API_KEY, TAILSCALE_TAILNET, TAILSCALE_MCP_HOST before connecting. You can also paste the ready-made client config above.

Does Tailscale RMCP (dinglebear-ai) run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Tailscale RMCP (dinglebear-ai)