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 VS Code Copilot?
GitHub Copilot Agent mode brings Tailscale data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 13 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Tailscale in VS Code Copilot
Tailscale and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Tailscale to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Kizeo Forms
9 toolsManage mobile forms, data submissions, and users via the Kizeo Forms API.

Gumroad
10 toolsAutomate e-commerce via Gumroad — manage products, sales, and license verification directly from any AI agent.

Zapier
6 toolsMonitor automated workflows, audit app connections, and search for Zap templates on Zapier — the leader in AI orchestration.

Afterpay
5 toolsBuy Now, Pay Later orchestration — manage checkouts, payments, and refunds via AI.
