ZeroTier MCP for AI. Manage your entire virtual network topology from text.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
ZeroTier MCP lets your AI agent manage entire virtual networks, acting as an automated interface to ZeroTier Central and local nodes.
You can list global networks, authorize specific members, check local node status, or manually join/leave project-specific VPNs—all without touching a dashboard.
It's full network control for your agent.
What your AI can do
List central network members
Retrieves a list of every member currently associated with a specified ZeroTier Central network.
Get central network
Retrieves detailed configuration information for a specific ZeroTier Central network.
List central networks
Lists all virtual networks managed under the primary ZeroTier Central account.
List every ZeroTier Central network or all networks the local node is currently connected to.
Authorize, de-authorize, or update specific member configurations across central and local controller networks.
Determine the current operational status, version, and network membership of the machine running your agent.
Programmatically join or leave a specific virtual network from your terminal via the AI agent.
List all known connected peers and available network paths to debug connectivity issues instantly.
Ask an AI about this
Waiting for input…
ZeroTier: 13 Network Management Tools
Use these tools to query network details, check local node status, join networks, or manage member configurations across ZeroTier Central.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using ZeroTier on VinkiusList Central Network Members
Retrieves a list of every member currently associated with a specified ZeroTier Central network.
Get Central Network
Retrieves detailed configuration information for a specific ZeroTier Central network.
List Central Networks
Lists all virtual networks managed under the primary ZeroTier Central account.
Update Central Network Member
Modifies the configuration or authorization status of a member in a ZeroTier Central...
List Controller Network Members
Retrieves a list of members on a network managed by a local controller instance.
List Controller Networks
Lists all networks that are being programmatically managed by the local controller.
Update Controller Network Member
Authorizes or configures a specific member within a locally managed network.
Update Controller Network
Creates or modifies an entire network configuration on a local controller instance.
Join Local Network
Connects the local machine to a specified ZeroTier virtual network.
Leave Local Network
Disconnects the local node from its current ZeroTier virtual network.
List Local Networks
Displays all virtual networks that the current local ZeroTier node is a member of.
List Local Peers
Lists every known peer and available network path directly from the local machine's perspective.
Get Local Status
Gets the current operational status and version of the local ZeroTier node running on this machine.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with ZeroTier, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ZeroTier. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 13 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Managing network access used to be a painful sequence of clicks and tokens.
Today, updating permissions or checking node connectivity means logging into multiple web dashboards. You copy IDs from one screen, paste them into another form, wait for confirmation messages, and then check an entirely separate terminal just to confirm the change actually stuck. It’s tedious, slow, and prone to human error.
Now, you simply tell your agent what needs fixing. The MCP handles the sequence of actions: it checks the central registry, confirms the node status locally, executes the update via `update_central_network_member`, and verifies everything worked—all in one conversation. You get reliable network state changes with natural language input.
Getting an instant overview of your local machine's connection points.
Before, figuring out if a node was connected or what its peer paths were required running multiple `ipconfig` commands and manually cross-referencing network logs. You had to stitch together the 'is it up?' answer from one tool and the 'where is it going?' answer from another.
Now, you run `list_local_peers`. It immediately gives you a consolidated view of all known connections and paths available on your machine. The whole process moves from manual log analysis to single-prompt query.
What your AI can actually do with this
This MCP connects your AI client directly to the operational side of ZeroTier. Think of it as giving your agent a command line view into your entire software-defined networking setup, bridging the gap between central management and local node operations.
Your agent can list all global networks and fetch detailed configurations from Central. It also handles immediate member authorization or de-authorization for nodes on private networks using their Member IDs. On the local machine side, you can check network status, join a specific virtual network, or discover known peers to troubleshoot connectivity issues in real time.
Since Vinkius manages all credentials through a zero-trust proxy, your keys never sit on a disk; they only pass through for immediate use when communicating with ZeroTier Central.
The real power is chaining this MCP with other services—for instance, combining it with a messaging MCP to automatically notify a team member whenever update_central_network_member fails. You build automations that span multiple platforms using your agent.
019e3911-5926-72a1-9270-73080661aa20 Here's how it actually works
The bottom line is that you manage global area networks from natural language commands, making manual API calls obsolete.
First, connect your preferred AI client by providing the ZeroTier Central API Token (and optionally a local authtoken).
Next, instruct your agent to perform an action, like listing all networks or authorizing a member ID.
Finally, the MCP executes the command and returns structured data detailing network status or confirmation of the change.
Who is this actually for?
The DevOps engineer who gets tired of jumping between Central dashboards and SSH sessions. The network admin who needs to audit node status quickly during an outage. Anyone managing multiple project environments across different virtual networks.
Automates the provisioning, authorization, and decommissioning of new nodes for secure SD-WAN deployments.
Monitors network health, checks peer connectivity, and manages network topologies without leaving their IDE or terminal.
Quickly joins or switches between project-specific virtual networks during development cycles.
What Changes When You Connect
You get centralized oversight: Use list_central_networks and get_central_network to see the status of all global networks in one go. No more opening multiple dashboards just to check IDs.
Local troubleshooting is instant: Instead of running manual CLI commands, ask your agent what's wrong. It can use list_local_peers to map out connectivity issues immediately.
Membership control becomes effortless: Need to authorize a node? Simply call update_central_network_member through the agent instead of navigating complex web forms.
Resilience in design: You don't need central connectivity for everything. Use local tools like join_local_network and list_local_peers when you only need to manage your physical node status.
Cross-platform automation: The true value is chaining this MCP with a messaging service. When update_controller_network_member runs, the agent can automatically send a success notification via Slack.
Reduced friction: By connecting through Vinkius's zero-trust proxy, your credentials are used only in transit and never stored on disk, keeping your key management clean.
See it in action
Onboarding a new team member to the VPN
The agent runs: 'Authorize user 10a2b3c4d5 on network X.' This calls update_central_network_member and confirms they have access, eliminating manual administrative tasks.
Debugging a failed remote connection
The agent runs: 'What are the peers for my current node?' This executes list_local_peers, providing an immediate map of known paths and helping diagnose why connectivity is failing.
Auditing all active projects
Instead of manually checking every ZeroTier dashboard, you ask the agent to run list_central_networks and get a full inventory list for compliance checks.
Switching work environments mid-day
You tell your agent: 'I need to switch to the QA network.' It executes leave_local_network followed by join_local_network, handling state changes automatically.
The honest tradeoffs
Trying to update local networks from Central
A user might try to use a central tool like update_central_network_member when the node is physically offline or disconnected.
Always check the state first. Use get_local_status before attempting any changes, ensuring your local machine can actually communicate with ZeroTier Central.
Listing all networks without context
Running only list_central_networks gives you a list of IDs but tells you nothing about which one is currently active or usable.
Combine calls. List the networks with list_central_networks, then immediately check local membership using list_local_networks to validate readiness.
Manually joining multiple times
A user repeatedly calls join_local_network because they think the previous join failed, leading to unnecessary errors and state confusion.
After leaving a network with leave_local_network, check the status using get_local_status. If it reports connected, you're good to go. Don't guess.
When It Fits, When It Doesn't
Use this MCP if your job involves managing multiple virtual access points or running complex decentralized services that require both global oversight and local resilience. For example, use list_central_networks for the audit; then use list_local_peers to check the operational reality of a single node. Don't use this if you only need to monitor simple IP ranges—that’s a dedicated inventory tool. If your goal is just to view configuration details without making changes, stick to get_central_network. If you are building an automation that needs to react to state changes (e.g., 'if status is down, then update member'), this MCP provides all the necessary inputs.
Questions you might have
How do I check if my node is connected using get_local_status? +
The get_local_status tool gives you the current operational status, version number, and tells you exactly how many networks your local node is joined to. It's a quick health check.
Can I list all my ZeroTier Central networks using list_central_networks? +
Yes, list_central_networks retrieves an inventory of every network ID and name managed under your main central account. It's the first step in auditing.
What is the difference between list_local_peers and list_local_networks? +
list_local_networks tells you which virtual networks your node belongs to. list_local_peers lists the actual, known peer addresses and paths for troubleshooting connectivity.
How do I manually authorize a member using update_central_network_member? +
You provide the target network ID and the Member ID you want to authorize. The tool attempts to modify the configuration, giving instant confirmation or an error code.
How do I manage my connection state using `join_local_network` or `leave_local_network`? +
These tools handle the active joining or leaving of networks. Use join_local_network when you need to connect your node to a new virtual network ID, and use leave_local_network if you want to disconnect entirely.
What information can I get about a specific network using `get_central_network`? +
This tool retrieves the full configuration details for one ZeroTier Central network. It’s useful when you know the ID and need to inspect the exact settings without listing all networks first.
When should I use `list_controller_networks` versus listing central networks? +
The difference is scope: list_central_networks shows your global ZeroTier Central infrastructure. By contrast, list_controller_networks only lists the local network definitions managed by a dedicated controller attached to your machine.
If I run into issues listing members using `list_central_network_members`, what should I check? +
First, verify the Network ID is correct. If the ID is valid but no members exist, the tool will return an empty list or a count of zero. Always ensure your API token has read access to that specific network.
Can I authorize a new device to join my network using the AI? +
Yes. You can use the update_central_network_member tool. Just provide the Network ID and the Member ID, and set the authorized parameter to true.
How do I check if my local ZeroTier service is running correctly? +
Ask the agent to run get_local_status. It will return your node's address, version, and online status directly from the local service.
Can I see which peers my node is currently connected to? +
Yes, the list_local_peers tool retrieves all known peers and their connection paths from your local ZeroTier node.
We've already built the connector for ZeroTier. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 13 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.