Developer · Local MCP server
Tailscale
Drive a Tailscale node and its tailnet through the CLI and the control-plane API.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.tailscale-mcp/tailscale-mcp- Version
- 1.3.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm, OCI image (Docker)
- Published
- 2026-09-07
- Updated
- 2026-09-07
- Publisher
- tailscale-mcp (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/tailscale-mcp) · how
- Website
- github.com/tailscale-mcp/tailscale-mcp
- Repository
- github.com/tailscale-mcp/tailscale-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @tailscale-mcp/tailscale-mcp | 1.3.1 | stdio |
| OCI image (Docker) | ghcr.io/tailscale-mcp/tailscale-mcp:1.3.1 | - | stdio |
How to connect Tailscale
Tailscale runs locally from a Node.js package published to the npm registry: @tailscale-mcp/tailscale-mcp version 1.3.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @tailscale-mcp/tailscale-mcp@1.3.1. It reads these environment variables: TAILSCALE_API_KEY (secret), TAILSCALE_OAUTH_CLIENT_ID, TAILSCALE_OAUTH_CLIENT_SECRET (secret), TAILSCALE_TAILNET, TAILSCALE_MCP_PRESET, TAILSCALE_MCP_ALLOW_WRITE and TAILSCALE_MCP_ALLOW_DESTRUCTIVE; set them in the client's configuration for this server.
Tailscale runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/tailscale-mcp/tailscale-mcp:1.3.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e TAILSCALE_API_KEY -e TAILSCALE_OAUTH_CLIENT_ID -e TAILSCALE_OAUTH_CLIENT_SECRET -e TAILSCALE_TAILNET -e TAILSCALE_MCP_PRESET -e TAILSCALE_MCP_ALLOW_WRITE -e TAILSCALE_MCP_ALLOW_DESTRUCTIVE ghcr.io/tailscale-mcp/tailscale-mcp:1.3.1. It reads these environment variables: TAILSCALE_API_KEY (secret), TAILSCALE_OAUTH_CLIENT_ID, TAILSCALE_OAUTH_CLIENT_SECRET (secret), TAILSCALE_TAILNET, TAILSCALE_MCP_PRESET, TAILSCALE_MCP_ALLOW_WRITE and TAILSCALE_MCP_ALLOW_DESTRUCTIVE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"tailscale-mcp": {
"command": "npx",
"args": [
"-y",
"@tailscale-mcp/tailscale-mcp@1.3.1"
],
"env": {
"TAILSCALE_API_KEY": "<secret>",
"TAILSCALE_OAUTH_CLIENT_ID": "<value>",
"TAILSCALE_OAUTH_CLIENT_SECRET": "<secret>",
"TAILSCALE_TAILNET": "<value>",
"TAILSCALE_MCP_PRESET": "<value>",
"TAILSCALE_MCP_ALLOW_WRITE": "<value>",
"TAILSCALE_MCP_ALLOW_DESTRUCTIVE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Tablebridge MCPQuery a folder of CSV / Parquet / JSON files with SQL - one queryable source, read-only. | Local · stdio |
| Tablecloth MCPOpen Korean e-Gov and finance sites in a clean, disposable Windows Sandbox with security programs. | Local · stdio |
| TabulaCross-AI personal memory. Save once in ChatGPT, recall in Claude, Mistral, Grok, or any MCP client. | Remote · HTTPLive check: sign-in required |
| Tada: automated QA for AI-written codeYour coding agent asks Tada to work through a feature in a real browser and gets back a verdict. | Local · stdio |
| TailscaleRead devices, users, keys, ACLs and DNS for a tailnet; manage devices, routes and auth keys. | Remote · HTTPLive check: ✓ handshake |
| Tailscale ComputeRun builds, tests, and benchmarks on your own Tailscale compute node. | Local · stdio |
| Tailscale MCP ServerSecure MCP access for private infrastructure over Tailscale - 48 tools across 9 domains. | Local · stdio |
| Tailscale RMCPTailscale device, route, DNS, key, user, and ACL management over MCP and CLI. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |