Tailscale RMCP is listed as active in the registry but did not answer our last check. 46 installs a week from npm. Last commit 11 Aug 2026.
Tailscale device, route, DNS, key, user, and ACL management over MCP and CLI.
We read the source, 17 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node scripts/install.js
const install = spawnSync(process.execPath, [installer], { stdio: "inherit" });
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
if std::path::Path::new("/.dockerenv").exists()
credentials_file="$HOME/.aws/credentials"
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 16 min ago.
claude mcp add rtailscale --transport http https://ts.dinglebear.ai/mcp
{
"mcpServers": {
"rtailscale": {
"url": "https://ts.dinglebear.ai/mcp"
}
}
}
[mcp_servers.rtailscale]
url = "https://ts.dinglebear.ai/mcp"
{
"mcpServers": {
"rtailscale": {
"url": "https://ts.dinglebear.ai/mcp"
}
}
}
{
"mcpServers": {
"rtailscale": {
"url": "https://ts.dinglebear.ai/mcp"
}
}
}
This one needs environment variables set before it will start:
TAILSCALE_API_KEY (Tailscale API key.), TAILSCALE_RMCP_VERSION (Optional GitHub release tag override for the downloaded Tailscale RMCP binary.), TAILSCALE_RMCP_REPO (Optional GitHub owner/repo override for release asset downloads.), TAILSCALE_RMCP_RELEASE_BASE_URL (Optional release download base URL override.), RUST_LOG (Tracing filter for Tailscale RMCP logs.).
The author declared them in the registry entry; get the values from the project itself.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://ts.dinglebear.ai/mcp | streamable-http | answering | 19737 ms | 16 min ago |
Rust MCP server and CLI for Tailscale devices, users, keys, policies, and auth.
Read devices, users, keys, ACLs and DNS for a tailnet; manage devices, routes and auth keys.
Gotify notifications and app, client, and message management over MCP and CLI.
Rust MCP server and CLI for Arcane Docker and container management.
Arcane Docker and Compose management over MCP and CLI with authenticated stdio and HTTP.
MCP server for NinjaONE RMM with device management, monitoring, and automation
Rust MCP server and CLI for Gotify push notifications and message management.
Sling CLI MCP server for data pipeline and replication management
Answers built from our own checks of this server.