Tailscale MCP Server

MCP开发工具

提供方 paulsmith

开发工具 未标注 无需鉴权 社区 / 第三方 Claude DesktopClaude

MCP server for safe read-only operations on the Tailscale CLI

一句话选型结论

按资料字段整理

Tailscale MCP Server 属于开发工具类 MCP 服务器,传输方式未标注,无需鉴权,可直接接入 Claude Desktop、Claude,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权无需鉴权 部署方式未标注
GitHub 星标 10 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

developer-toolstailscalemcpserver网络管理Go本地部署只读访问

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Tailscale MCP Server当前 未标注 未标注 未标注 无 2026-05-18
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方paulsmith上游标注的维护方 paulsmith
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-18上游最后核验时间

详细介绍

7.1 KB
来自项目仓库与上游目录的原文,未做删改

Tailscale Model Context Protocol (MCP) Server

A simple MCP server that
provides read-only access to your Tailscale network
directly from Claude Desktop and other MCP-compatible clients.

> [!CAUTION]
> You might not want to do this! This server exposes your Tailscale network to
> an external application. It invokes the tailscale binary on your system on
> your behalf, assembling an argument list through string concatenation, and
> executing as your logged-in Tailscale account. While its operation is
> intended to be read-only and therefore "secure", you should be aware of the
> potential risks involved in exposing any part of your network to third-party
> applications. Especially when interacting with
> LLMs.

Description

This server allows, for example, Claude to interact with your Tailscale network
by exposing read-only commands as tools and prompts. It enables you to:

  • Check your Tailscale status and connected devices
  • Get network diagnostics
  • View your Tailscale IP addresses
  • List available exit nodes
  • Ping Tailscale hosts
  • Look up information about Tailscale IPs

Requirements

  • Go (for building from source)
  • Tailscale CLI must be installed and
    accessible in your $PATH
  • An MCP-compatible client like Claude Desktop

Installation

Pre-built Binary

Coming soon

Building from Source```bash

go install github.com/paulsmith/tailscale-mcp-server@latest


## Using with Claude Desktop

1. First, make sure you have Claude Desktop
   installed and updated to the latest version

2. Open your Claude Desktop configuration file:
   - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
   - Windows: `%APPDATA%\Claude\claude_desktop_config.json`

3. Add the Tailscale MCP server configuration:```json
{
  "mcpServers": {
    "tailscale": {
      "command": "tailscale-mcp-server"
    }
  }
}
  1. Make sure tailscale-mcp-server is on your $PATH, or provide the full
    path to the binary in the command field.

  2. Restart Claude Desktop

Available Tools

The server exposes the following tools:

  • tailscale: Run any "safe" Tailscale command
  • get-ip: Get your Tailscale IP addresses
  • get-status: Get information about your Tailscale network
  • network-check: Check Tailscale network connectivity
  • list-exit-nodes: List available Tailscale exit nodes
  • ip-lookup: Look up information about a Tailscale IP
  • ping-host: Ping a Tailscale host
  • dns-status: Get DNS diagnostic information

The List of Safe Subcommands

The list of subcommands that are considered "safe" and can be run through the
tailscale tool that this MCP server uses are:

  • netcheck
  • ip
  • dns status
  • status
  • metrics
  • ping
  • version
  • exit-node list
  • whois

Available Prompts

The server also includes several prompts to help with common tasks:

  • diagnose-network: Analyze Tailscale network connectivity issues
  • analyze-peers: Get a summary of devices in your tailnet
  • exit-node-recommendations: Get recommendations for exit nodes

Example Usage

Once connected to Claude Desktop, you can ask questions like:

  • "What's my Tailscale IP address?"
  • "Show me all the devices connected to my Tailscale network"
  • "Can you check if my Tailscale network connection is working properly?"
  • "Ping my device called 'laptop'"
  • "Are there any exit nodes available in my network?"
  • "What DNS settings is Tailscale using?"

Example Chat

> Describe my tailnet and note anything out of the ordinary.

(Some content elided)```markdown
I'll check your Tailscale network status and provide you with information about
your tailnet. Let me run a few commands to gather the details.

First, let's check the overall status of your tailnet:

> View result from get-status ...

Now, let's get the Tailscale IP addresses:

> View result from get-ip ...

Let's check the network connectivity status:

> View result from network-check ...

Let's check for available exit nodes in your tailnet:

> View result from list-exit-nodes ...

Let's also check the DNS status:

> View result from dns-status ...

Based on all the information gathered, here's a description of your tailnet:

Your tailnet is named "orca-arctic.ts.net" and currently has 11 devices
registered, with 6 devices currently online and 5 offline. Your current device
is "venus" running macOS with the IP address 100.86.102.37.

Here's what I've observed about your tailnet:

  • You have one device ("bunny") configured as an exit node. This allows other
    devices to route their traffic through it.
  • There's a version mismatch between your client (1.80.3) and the tailscaled
    server (1.82.0), which could be worth updating to ensure compatibility and
    security.
  • You have a device named "hello.ts.net" with a different user account (hello@)
    compared to your other devices (paulsmith@). This might be unusual if you're
    not expecting another user in your tailnet.
  • Your network connectivity looks good with both IPv4 and IPv6 support, and
    you're using UPnP for port mapping.
  • Your nearest DERP (Designated Encrypted Relay for Packets) server is in
    Ashburn with a 71.9ms latency, which is quite good.
  • MagicDNS is enabled tailnet-wide, allowing you to reach devices by their
    hostname (e.g., venus.orca-arctic.ts.net).
  • You're using NextDNS as your DNS resolver, which is a custom configuration.

Notable items that might need attention:

  • The client/server version mismatch mentioned above
  • The device "hello.ts.net" with a different user account (hello@) that might
    need verification if it's not expected
  • Five of your devices are currently offline, which is normal if they're not in
    use but worth checking if you expect them to be online

Would you like me to provide more information about any specific aspect of your
tailnet?
```

Security Notes

  • This server allows read-only access to your Tailscale network
  • Only subcommands of the tailscale CLI in the "safe" whitelist are permitted
  • No configuration changes can be made (in theory!)
  • All commands are executed with your user's permissions
  • You are exposing your Tailscale network to an LLM, however indirectly via the
    MCP RPC, which is subject to security risks such as prompt injection -
    educate yourself

Troubleshooting

Server not appearing in Claude Desktop

Check the following:

  1. Make sure the path to the binary in your configuration is correct
  2. Verify Tailscale CLI is installed and accessible in your $PATH
  3. Check Claude Desktop logs for errors:
    - macOS: ~/Library/Logs/Claude/mcp*.log
    - Windows: %APPDATA%\Claude\logs\mcp*.log

Command errors

If commands are failing, try:

  1. Running the command directly using the Tailscale CLI to verify it works
  2. Check that your Tailscale is correctly configured and connected
  3. Ensure the command is in the allowed safe list

Development

This server is built using the mcp-go
package. If you want to extend or modify it:

  1. Clone the repository
  2. Make your changes
  3. Build using go build
  4. Test with Claude Desktop or other MCP clients

Contributing

Contributions are welcome! Please feel free to open an issue and/or submit a
pull request.

License

MIT License

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Tailscale MCP Server 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Tailscale MCP Server 怎么在 Claude Desktop、Claude 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Tailscale MCP Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Tailscale MCP Server 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Tailscale MCP Server 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Tailscale MCP Server 能提供哪些能力?

资料显示能力标签包括 只读访问、Go、Claude、网络管理。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-18。