How do I connect Tailscale MCP Server to Claude?

Run `claude mcp add tailscale-mcp -- npx -y --package=@hexsleeves/tailscale-mcp-server tailscale-mcp-server` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.

Is Tailscale MCP Server free?

The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.

What can Tailscale MCP Server do?

Tailscale MCP Server documents 9 tools to the agent, including connect_network, device_action, disconnect_network. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

Tailscale MCP

Unclaimed

by HexSleeves

server that provides seamless integration with Tailscale's CLI commands and REST API, enabling automated network management and monitoring through a standardized interface

Set up this server

Compare servers My Stack

01 / Choose your client

02 / Before you connect

Authentication is not specified. Check the project instructions before connecting.

Install the runtime required by the project and make it available to your client.

Project instructionsEnvironment variable names (optional)

Use names from the project instructions, separated by commas. Enter names only, never secret values.

03 / Add the configuration

Source: generated from public install instructions

claude mcp add --transport stdio 'tailscale-mcp' -- 'npx' '-y' '--package=@hexsleeves/tailscale-mcp-server' 'tailscale-mcp-server'

Run in your terminal after replacing any placeholders.

04 / Check it in your client

Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.

mcpmcp-serverstailscale

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

9 of 9 tools

Documented tools (9)

From project documentation. A server handshake does not verify each tool’s description or behavior.

connect_network

Connect to the Tailscale network

device_action

Perform actions on specific devices (authorize, deauthorize, delete, expire-key)

disconnect_network

Disconnect from the Tailscale network

get_network_status

Get current network status from Tailscale CLI

get_tailnet_info

Get detailed network information

get_version

Get Tailscale version information

list_devices

List all devices in the Tailscale network

manage_routes

Enable or disable routes for devices

ping_peer

Ping a peer device

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Tailscale MCP Server

How do I connect Tailscale MCP Server to Claude?: Run `claude mcp add tailscale-mcp -- npx -y --package=@hexsleeves/tailscale-mcp-server tailscale-mcp-server` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
Is Tailscale MCP Server free?: The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Tailscale MCP Server do?: Tailscale MCP Server documents 9 tools to the agent, including connect_network, device_action, disconnect_network. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.