home / mcp / mcp tailscale server

MCP Tailscale Server

Provides read-only access to Tailnet devices, statuses, updates, and summaries via MCP clients.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "aplaceforallmystuff-mcp-tailscale": {
      "command": "node",
      "args": [
        "/absolute/path/to/mcp-tailscale/dist/index.js"
      ],
      "env": {
        "TAILSCALE_API_KEY": "tskey-api-your-key-here"
      }
    }
  }
}

You can manage your Tailscale tailnet through an MCP server that exposes device listings, status, updates, and network summaries to Claude Code and other MCP clients. This server provides a practical way to view and monitor devices, check health, and stay informed about available updates without altering your Tailnet configuration.

How to use

You interact with the MCP server through your MCP client by selecting the Tailscale MCP server and issuing queries or commands. Use it to list all devices, view details about a specific device, filter online or offline devices, check for updates, and get a summary of your tailnet. The server provides read-only access to your Tailscale data and does not modify your setup.

Key capabilities you can use include: list devices, get device details, list online devices, list offline devices, check which devices need updates, and retrieve a network summary.

How to install

# Prerequisites
node >= 14
npm >= 6

# Install dependencies
npm install

# Build the project
npm run build

# Run tests locally (optional)
TAILSCALE_API_KEY=your-key node dist/index.js

Configuration and usage notes

This MCP server requires your Tailscale API key to read device information. You must provide the key through an environment variable when running the server.

Environment variable to set: TAILSCALE_API_KEY.

Optional tailnet customization can be done by setting TAILSCALE_TAILNET to your tailnet name; if not provided, the current user’s tailnet is used by default.

Other important notes

Only read-only API calls are used, so this server does not modify your Tailnet configuration. Keep your API key secure; do not commit it to version control.

Two configuration approaches are supported for the MCP client: a local stdio (direct node process) configuration and a Claude Desktop configuration. Each approach starts a node process that runs the MCP server from its built distribution.

Troubleshooting

If you cannot connect, verify that your TAILSCALE_API_KEY is valid and that it has the necessary read permissions. Ensure your Node environment can access network resources to reach Tail’s API endpoints.

Check that the MCP client is configured to use the correct stdio command and the path to your built server distribution.

Available tools

tailscale_list_devices

List all devices in your tailnet with detailed information.

tailscale_get_device

Get details about a specific device by ID or name.

tailscale_list_online_devices

List only devices that are currently online/connected.

tailscale_list_offline_devices

List only devices that are offline or disconnected.

tailscale_check_updates

Check which devices have Tailscale client updates available.

tailscale_device_summary

Get summary statistics about online/offline counts and OS distribution.