Tailscale MCP server
Tailscale in any MCP client, through Memtro: Tailscale does not publish this server. Memtro's Tailscale connector reads Tailscale through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Tailscale tailnet: devices with owner, OS, addresses, tags, online state, last seen and key expiry, a device's subnet routes, the people on the tailnet with role and device count, and API and auth key metadata (never the keys themselves). Can authorise or de-authorise, rename, tag or remove a device, set its enabled subnet routes and turn its key expiry on or off.
Reads
tailscale_list_devicesDevices on the tailnet: name, hostname, owner, OS, Tailscale addresses, tags, whether online, last seen, key expiry (and whether it has expired)…tailscale_get_deviceOne device in detail, with the subnet routes it advertises and those that are enabled for it.tailscale_list_usersPeople on the tailnet: name, login, role (owner, admin, member, it-admin, network-admin, billing-admin, auditor), whether a member or shared in…tailscale_list_keysAPI access tokens and auth keys on the tailnet, as metadata only: id, type, description, created, expiry (and whether expired), revoked…tailscale_get_settingsThe tailnet's settings: whether new devices and users need approval, device key duration in days, auto-updates, HTTPS certificates…
Acts, when you ask
These change something in Tailscale. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
tailscale_authorize_deviceAuthorises a device on the tailnet (where device approval is on), or with authorized false de-authorises it, which cuts it off the tailnet at once.tailscale_rename_deviceRenames a device on the tailnet (its MagicDNS name).tailscale_set_device_tagsReplaces every ACL tag on a device with the list given.tailscale_set_device_routesSets which of a device's advertised subnet routes are enabled, replacing the enabled list (0.0.0.0/0 and ::/0 make it an exit node).tailscale_set_device_key_expiryTurns a device's key expiry off (key_expiry_disabled true: it never has to re-authenticate) or back on (false: the original expiry applies again…tailscale_delete_deviceRemoves a device from the tailnet.
Connect it
First connect Tailscale on Dashboard → Connections, then add Memtro to your client once. The Tailscale tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Tailscale connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which machines on the tailnet are offline right now?
- › Whose device keys expire this month?
- › What is the Tailscale address of the build server?
- › Which auth keys exist, and which of them are reusable?
- › Remove the contractor's laptop from the tailnet
Questions
- Is this an official Tailscale MCP server?
- No. It is Memtro's MCP server with Memtro's Tailscale connector behind it: the connector reads Tailscale through its API with the credentials you connect on Dashboard → Connections, and Tailscale publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Tailscale?
- Only when you ask, and only what it has been granted: authorise or de-authorise a device on the tailnet; rename a device; replace a device's ACL tags; set a device's enabled subnet routes; turn a device's key expiry off or back on; remove a device from the tailnet. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.