mcp server
Tailscale RMCP
Tailscale device, route, DNS, key, user, and ACL management over MCP and CLI.
Description as published by the maintainer. Source
- version 0.1.4
- active
active — Most recent push to the repository was 2026-08-05.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 4 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-05 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 2 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Package downloads | 119 downloads | Package downloads from the npm registry in this window. Includes continuous integration runs, mirrors and automated installs, so it overstates the number of human users. | 2026-07-30 to 2026-08-05 | npm | |
| Latest published version | 0.1.4 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-04 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | AGPL-3.0 | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-08-04 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
Tailscale RMCP
— last commit 2026-08-05, shares automation, claude-code-plugins, cli
Rust MCP server and CLI for Tailscale devices, users, keys, policies, and auth.
-
UniFi RMCP
— last commit 2026-08-05, shares automation, claude-code-plugins, cli
Rust MCP server and CLI for UniFi Network controller operations.
-
UniFi RMCP
— last commit 2026-08-05, shares automation, claude-code-plugins, cli
Rust MCP server and CLI for UniFi Network controller operations.
-
Apprise RMCP
— last commit 2026-08-05, shares automation, claude-code-plugins, cli
Rust MCP server and CLI for Apprise notification fan-out across dozens of delivery backends.
-
Arcane RMCP
— last commit 2026-08-05, shares automation, claude-code-plugins, cli
Rust MCP server and CLI for Arcane Docker and container management.
-
Gotify RMCP
— last commit 2026-08-05, shares automation, claude-code-plugins, cli
Rust MCP server and CLI for Gotify push notifications and message management.
-
Apprise RMCP
— last commit 2026-08-05, shares automation, claude-code-plugins, cli
Apprise notifications over MCP and CLI with authenticated stdio and HTTP transports.
-
Arcane RMCP
— last commit 2026-08-05, shares automation, claude-code-plugins, cli
Arcane Docker and Compose management over MCP and CLI with authenticated stdio and HTTP.
-
Gotify RMCP
— last commit 2026-08-05, shares automation, claude-code-plugins, cli
Gotify notifications and app, client, and message management over MCP and CLI.
-
Soma
— last commit 2026-08-06, shares automation, cli, http-server
RMCP runtime for provider-backed agents with CLI, REST, HTTP MCP, plugins, and scaffold support.
These share tags the maintainers applied themselves, such as automation, claude-code-plugins, cli, device-management. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
Also from dinglebear-ai
-
Cortex RMCP
— last commit 2026-08-05
Self-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS.
-
Labby
— last commit 2026-08-06
Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI.
-
YTDL RMCP
— last commit 2026-08-06
yt-dlp search, download, metadata, delivery, and Plex workflows over MCP and CLI.
-
Synapse RMCP
— last commit 2026-08-05
Host, Docker, Compose, SSH, logs, ZFS, and file operations over MCP and CLI.
-
Unraid RMCP
— last commit 2026-08-05
Rust MCP server and CLI for Unraid GraphQL operations across NAS, Docker, VM, and storage workflows.
-
Unraid MCP
— last commit 2026-08-05
MCP server for Unraid API — provides tools to interact with an Unraid server's GraphQL API.
-
Yarr MCP
— last commit 2026-08-06
Self-hosted media fleet operations across Sonarr, Radarr, Plex, and related apps over MCP and CLI.
How the author describes it
Topics the maintainer set on GitHub: automation, claude-code, claude-code-plugins, cli, codex, device-management, gemini, homelab, http-server, mcp, mcp-server, model-context-protocol, networking, oauth, rmcp, rust, tailnet, tailscale, vpn.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab