Bring Vpn
to Cursor
Learn how to connect Tailscale to Cursor and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 Cursor?
Cursor's Agent mode turns Tailscale into an in-editor superpower. Ask Cursor to generate code using live data from Tailscale and it fetches, processes, and writes. all in a single agentic loop. 13 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Tailscale in Cursor
Tailscale and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Tailscale to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Apptoto
6 toolsReduce no-shows with smart appointment reminders, automated confirmations, and two-way messaging for every booking.
Mapflow
7 toolsExtract geospatial features from satellite imagery with AI that detects buildings, roads, and vegetation patterns automatically.
Mingdao Cloud
10 toolsEnterprise zero-code application and workflow platform — manage worksheets, records, and automations via AI.
NCDC Climate Data Online
10 toolsAccess authoritative historical weather and climate data via NCDC — track datasets, stations, and climate records directly from your AI agent.