Tailscale Mcp
Manage Tailscale tailnet resources—devices, ACL context, and admin tasks—from your AI assistant via MCP.
Overview
tailscale-mcp is a MCP server for the Operate phase that connects AI assistants to Tailscale tailnet management from a stdio MCP host.
What is this MCP server?
- Tailscale-focused MCP server for tailnet management from chat-driven agents
- stdio npm package @yawlabs/tailscale-mcp (v0.12.8)
- Bridges AI assistants to Tailscale admin workflows you already run in the console
- Useful when solo builders mix cloud APIs, home lab, and private services on one tailnet
- Reduces context switch between Tailscale admin UI and agent-driven infra fixes
- npm package @yawlabs/tailscale-mcp at server version 0.12.8
- Transport: stdio per MCP server schema 2025-12-11
What problem does it solve?
When your app depends on a private tailnet, juggling Tailscale admin tasks and agent-driven coding slows fixes to connectivity and access issues.
Who is it for?
Solo builders running Tailscale between dev machines, VPS, and homelab services who want MCP-native tailnet admin.
Skip if: Teams not using Tailscale, or environments where tailnet API keys must never be available to coding agents.
What do I get? / Deliverables
After adding tailscale-mcp, your agent can help execute and explain tailnet management steps alongside infra and application changes.
- Agent-executed tailnet management actions you authorize
- Consolidated tailnet context for debugging private service reachability
- Fewer round trips between admin console and coding sessions
Recommended MCP Servers
Journey fit
Tailnet administration is ongoing infrastructure work after you adopt private networking for apps and homelab services. Tailscale changes affect how builders reach staging, databases, and home lab nodes—core infra operations, not launch SEO.
How it compares
MCP bridge to Tailscale admin APIs, not a VPN installer script or generic cloud IAM skill.
Common Questions / FAQ
Who is tailscale-mcp for?
Builders who already use Tailscale to reach staging, internal APIs, or home lab nodes and want agent-assisted tailnet management.
When should I use tailscale-mcp?
Use it during Operate when adjusting tailnet access, debugging private routes, or coordinating device state while shipping or supporting your app.
How do I add tailscale-mcp to my agent?
Install @yawlabs/tailscale-mcp, configure it as a stdio MCP server, and provide Tailscale API credentials with minimal scopes on a trusted machine.