Allows managing a Tailscale network (tailnet) by listing devices, checking online/offline status, monitoring connection health, viewing available client updates, and retrieving network summary statistics.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-tailscaleWhich of my devices are currently online?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-tailscale
MCP server for managing your Tailscale network (tailnet) through Claude Code and other MCP clients.
Features
List Devices - View all devices in your tailnet with detailed information
Device Status - Check online/offline status and connection health
Update Management - See which devices have Tailscale client updates available
Network Summary - Get overview statistics of your tailnet
Device Search - Find specific devices by ID, name, or hostname
Available Tools
Tool | Description |
| List all devices in your tailnet |
| Get details about a specific device |
| List only online/connected devices |
| List only offline/disconnected devices |
| Check which devices need updates |
| Get summary stats (online/offline, by OS, etc.) |
Installation
Configuration
Environment Variables
TAILSCALE_API_KEY- Required. Your Tailscale API key from https://login.tailscale.com/admin/settings/keysTAILSCALE_TAILNET- Optional. Defaults to-(your current user's tailnet)
Get an API Key
Click "Generate auth key"
Configure:
Expiry: Choose duration (1-90 days)
Description: "MCP Server"
Copy the key (starts with
tskey-api-)
Claude Desktop Configuration
Add to your claude_desktop_config.json:
Claude Code Configuration
Usage Examples
List All Devices
Check Online Devices
Check for Updates
Get Device Details
Network Summary
Development
API Permissions
This MCP server uses read-only API calls. It does not modify your Tailscale configuration. The API key only needs:
Device list access
Device status access
Security Notes
API keys are case-sensitive
Keys expire based on the duration you set
Store keys securely (never commit to version control)
Use environment variables or secure configuration management
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Changelog
See CHANGELOG.md for version history and release notes.
License
MIT License - see LICENSE for details.
Author
Jim Christian
Website: jimchristian.net
GitHub: @aplaceforallmystuff