Compatible with every major AI agent and IDE
What is the Tailscale MCP Server?
Connect your Tailscale network (tailnet) to any AI agent and take full control of your zero-trust infrastructure through natural conversation.
What you can do
- Device Management — List all nodes in your tailnet, fetch specific device details, authorize new machines, or update device tags to organize your fleet.
- Network Security (ACLs) — Retrieve and update your HuJSON policy files (ACLs) to manage access control without leaving your chat interface.
- Authentication Keys — List, create, and delete auth keys to automate node joining or manage ephemeral server access.
- User Auditing — List all users within your tailnet and fetch detailed profile information for specific members.
- Node Cleanup — Securely delete decommissioned devices from your tailnet using their unique IDs.
How it works
- Subscribe to this server
- Enter your Tailscale API Key
- Start managing your private network from Claude, Cursor, or any MCP-compatible client
No more jumping between the Tailscale admin console and your terminal. Your AI acts as a network administrator that understands your infrastructure context.
Who is this for?
- DevOps Engineers — quickly check node statuses, manage tags, and generate auth keys for CI/CD pipelines.
- Security Teams — audit tailnet users and inspect or update ACL policies to ensure zero-trust compliance.
- IT Administrators — authorize new devices and clean up old nodes from the network via simple commands.
Built-in capabilities (13)
Authorize Device
Create Auth Key
Delete Auth Key
Delete Device
Get Auth Key
Get Device Details
Get Tailnet Policy (ACL)
Get User
List Auth Keys
List Tailnet Devices
List Users
Update Device Tags
Update Tailnet Policy (ACL)
Why Claude Desktop?
Claude Desktop is the definitive way to connect Tailscale to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 13 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Tailscale in Claude Desktop
Tailscale and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Tailscale to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Tailscale in Claude Desktop
The Tailscale MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 13 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Tailscale for Claude Desktop
Every tool call from Claude Desktop to the Tailscale MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I update my network's security policy (ACL) using this server?
Yes! You can use get_tailnet_acl to view the current HuJSON policy and update_tailnet_acl to apply changes directly to your tailnet configuration.
How do I authorize a new device that is pending approval?
Use the authorize_device tool with the specific device_id and set the authorized parameter to true. This allows you to manage node entry without the admin console.
Is it possible to generate temporary authentication keys for my servers?
Absolutely. Use the create_auth_key tool. You can optionally provide capabilities like 'ephemeral' or 'reusable' in the JSON payload to define how the key should behave.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Webflow
10 toolsEquip your AI agent with direct access to Webflow — manage CMS collections, publish sites, and query site analytics without opening the Webflow designer.
Pixelfed (Instagram Alternative)
17 toolsManage your Pixelfed presence — post photos, interact with the community, and track notifications directly from any AI agent.

Amazon DynamoDB Table
5 toolsThis MCP does exactly one thing: it manages items in a single Amazon DynamoDB Table. That's its only function, and nothing else. Incredible for giving your AI a secure NoSQL database.

Linear
12 toolsStreamline issue tracking and project management via Linear — list teams, query issues, create comments and inspect cycles directly from any AI agent.
