TailscaleMCP
Exports Tailscale network metrics and monitoring data to Datadog for centralized observability and alerting.
Sends Tailscale network alerts and notifications to Discord channels via webhooks for device connection events and network monitoring.
Enables creation and export of Grafana dashboards for Tailscale network monitoring, including comprehensive network overview, device activity tracking, security monitoring, and network topology visualization dashboards.
Integrates with PagerDuty for incident management and alerting based on Tailscale network events and security monitoring.
Exports custom metrics for Tailscale network monitoring including device activity, network traffic, API performance, and health statistics that can be scraped by Prometheus for monitoring and alerting.
Sends Tailscale network alerts and notifications to Slack channels for device connection events and network monitoring.
Provides comprehensive management of Tailscale networks including device management (authorization, SSH access, tagging, exit nodes), DNS configuration (MagicDNS, custom records), file sharing via Taildrop, security auditing, monitoring and metrics collection, ACL management, and network topology visualization.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@TailscaleMCPlist all authorized devices in my network"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Tailscale MCP
Operate your tailnet from the AI tools you already use. Tailscale MCP is a FastMCP 3.1.0+ server that exposes the Tailscale Admin API to assistants and automation: devices, DNS, services, monitoring, Funnel, Taildrop-related flows, and more through a small set of portmanteau tools (many operations each, so your client does not drown in hundreds of tiny tool names). Optional SEP-1577 agentic workflows (run_agentic_tailnet_workflow) let a capable host run multi-step flows when sampling is configured. An optional Webapp (Vite/React) gives humans a glass-style dashboard: My tailnet topology, Partner tailnets insights, help, and connection status.
Repository: github.com/sandraschi/tailscale-mcp
Why this exists
If you manage a Tailscale tailnet, you already use the admin console and the official API. This project turns that surface into MCP tools so Cursor, Claude Desktop, Antigravity, or any MCP-capable client can list devices, inspect DNS, drive automation, and answer questions about your network with structured responses (success flags, errors, hints) instead of ad-hoc shell scripts.
You stay on the Admin API contract: the authoritative reference remains Tailscales API docs. The MCP server adds opinionated grouping, persistence for certain flows, optional LLM sampling for multi-step tasks, and an optional browser UI for quick visual checks.
Related MCP server: OpenAccess MCP
What you get
MCP tools (portmanteau pattern)
Instead of dozens of one-off tools, operations are grouped into verb-led domains such as manage_tailnet_devices, manage_tailnet_network, monitor_tailnet, manage_taildrop, manage_funnel, and more (security, automation, reporting, integrations, etc.). Each tool takes an operation argument similar in spirit to other fleet servers that avoid tool explosion. MCP names are verb-first; the redundant tailscale_ prefix is not used because this server is Tailscale-only.
Coverage includes device and user management, MagicDNS and network policies, Tailscale Services (TailVIPs) where exposed, monitoring and metrics, Funnel and Taildrop-related flows (with CLI integration where applicable), plus help, status, and partner tailnet summaries for orgs that share tailnets with partners.
The full matrix of tools and operations lives in docs/TAILSCALE_MCP_PORTMANTEAU_TOOLS.md (see the doc index for any additional reference material).
Agentic workflows (optional)
For multi-step automation, run_agentic_tailnet_workflow uses FastMCP sampling (SEP-1577). You can point the server at a local OpenAI-compatible endpoint (for example Ollama) via TAILSCALE_SAMPLING_*, or let the host run the LLM with TAILSCALE_SAMPLING_USE_CLIENT_LLM=1. Details and safety notes are in docs/PRD.md.
Webapp (optional)
The Webapp under web_sota/ is a React/Vite front end with a dark, glass-style layout. Highlights:
My tailnet visualize your network (Mermaid topology from
get_tailnet_status, plus a decorative Orbit view).Partner tailnets summary of members vs shared users and devices grouped by login, aligned with the
summarize_partner_tailnetstool.Help environment and sampling variables, linked from the shell.
Ports for this repo follow the fleet adjacency convention (10820 frontend / 10821 backend by default); see docs/WEBAPP.md and web_sota/start.ps1.
LM Link (Tailscale + LM Studio)
The get_lm_link tool provides operational control over LM Link — the Tailscale + LM Studio partnership (Feb 2026) that creates an encrypted mesh for remote local LLMs:
Operation | CLI equivalent | Description |
|
| Live peers, loaded models, link state |
|
| Toggle LM Link on/off |
|
| Rename this device on the link |
|
| Route model requests to a preferred peer |
| (static / Tailscale API) | Setup docs and tailnet connectivity check |
The LM Link webapp page (/lm-link) shows a live dashboard with peer lists,
loaded model badges, device rename, and preferred device selection. Requires the
lms CLI (bundled with LM Studio or via curl -fsSL https://lmstudio.ai/install.sh | bash).
Cross-repo: For model-level management, see local-llm-mcp which also probes LM Link status for its provider health dashboard.
Persistence and observability
DiskStore (FastMCP 3.1.0) holds durable state for funnels, transfers, and preferences across restarts see docs/STORAGE_BACKENDS.md. Optional Prometheus / Grafana / Loki-style stacks are documented under docs/monitoring/ if you want full observability on your own infrastructure.
Skills for agents
When present, skills/TAILSCALE_EXPERT.md is exposed as resource://tailscale/skills so clients can load operator-focused guidance alongside tools.
Who it is for
Platform engineers wiring tailnet changes into IDEs and automation.
Operators who want a quick dashboard plus MCP for deeper queries.
Agents (with appropriate allowlists) that should plan multi-step API work instead of one-shot guesses.
Requirements
You need a Tailscale API key with access to your tailnet and the tailnet name the key is scoped to:
Variable | Role |
| Bearer token from the admin console |
| Your tailnet identifier (as shown in the console / API) |
Optional variables for sampling, HTTP transport, and logging are documented in docs/PRD.md and .env.example.
If you are new to Tailscale itself, read docs/WHAT_IS_TAILSCALE.md first it explains tailnet vs Admin API vs client in plain language.
Quick Start
git clone https://github.com/sandraschi/tailscale-mcp
cd tailscale-mcp
justThis opens an interactive dashboard showing all available commands. Run just bootstrap to install dependencies, then just serve or just dev to start.
Manual Setup
If you don't have just installed:
Install (quick)
Full options (Claude Desktop JSON, Docker, Webapp) are in docs/INSTALL.md. Minimal path with uv:
git clone https://github.com/sandraschi/tailscale-mcp.git
cd tailscale-mcp
uv sync
uv run tailscale-mcpSet TAILSCALE_API_KEY and TAILSCALE_TAILNET in your environment or .env before starting.
Documentation map
Topic | Document |
Install, env, clients, Webapp | |
Tailscale concepts | |
Funnel / Taildrop / Services / Peer Relays — what each does, when to use it | |
Product scope and sampling | |
Webapp routes and ports | |
Architecture | |
Portmanteau tools (deep dive) | |
Everything else | |
Contributing (uv, Ruff, tests) |
🛡️ Industrial Quality Stack
This project adheres to SOTA 14.1 industrial standards for high-fidelity agentic orchestration:
Python (Core): Ruff for linting and formatting. Zero-tolerance for
printstatements in core handlers (T201).Webapp (UI): Biome for sub-millisecond linting. Strict
noConsoleLogenforcement.Protocol Compliance: Hardened
stdout/stderrisolation to ensure crash-resistant JSON-RPC communication.Automation: Justfile recipes for all fleet operations (
just lint,just fix,just dev).Security: Automated audits via
banditandsafety.
License
MIT see LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceProvides dynamic access to 400+ Meraki Dashboard API endpoints with intelligent discovery, plus advanced compliance auditing (PCI DSS, HIPAA, SOC2, ISO 27001, NIST), backup/restore operations, and network security analysis. Enables natural language queries to manage Meraki networks without pre-defined tools.3
- Alicense-qualityDmaintenanceEnables secure remote access operations through SSH, SFTP, rsync, VPN, and tunneling with enterprise-grade policy enforcement and audit logging. Provides AI assistants with secure, policy-driven access to remote systems while maintaining comprehensive audit trails and zero-trust security.1Apache 2.0
- AlicenseAqualityCmaintenanceProduction-ready MCP server for Tailscale management with 48 tools across 9 domains: Devices, DNS/Split DNS, ACL policies, Auth Keys, Users, Webhooks, Posture Integrations, Tailnet Settings, and Diagnostics. Supports stdio and SSE transport with Bearer token authentication. Built with TypeScript strict mode, Zod validation, and zero shell execution. AGPL-3.0 + Commercial dual-licensed.49931AGPL 3.0
- AlicenseAqualityAmaintenanceEnables AI agents to securely interact with Tailscale tailnets for device inventory, ACL review, key hygiene, and more, with token-efficient output and write-gated mutations.19MIT
Related MCP Connectors
Tailscale device, route, DNS, key, user, and ACL management over MCP and CLI.
Enterprise AI Control Plane: governance, guardrails, spend tracking, compliance & smart routing.
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/tailscale-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server