mcp-reconnect vs Tailscale
mcp-reconnect is a plugin bundle for AI coding tools published by palios-taey. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Tailscale is an MCP server published by tailscale-mcp. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  mcp-reconnect |  Tailscale |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.2.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.5 Downloads/month (npm): 1 641 Downloads/week (npm): 531 Forks (GitHub): 3 Stars (GitHub): 16 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.0.5 Downloads/month (npm): 1 641 Downloads/week (npm): 531 Forks (GitHub): 3 Stars (GitHub): 16 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | mcp-reconnect | Tailscale |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (worse) | 16 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release (differs) | Not published | 2026-10-26 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@tailscale-mcp/tailscale-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 7, secrets among them: 2 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/palios-taey/mcp-reconnect | github.com/tailscale-mcp/tailscale-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
mcp-reconnect
Reconnect MCP servers in Claude Code tmux sessions via automated key injection. No API required — works by driving the /mcp interactive menu through tmux send-keys.
Tailscale
Drive a Tailscale node and its tailnet through the CLI and the control-plane API
How to run each
mcp-reconnect As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mcp-reconnect@claude-communityTailscale As a local MCP server: npm package
claude mcp add --env "TAILSCALE_API_KEY=<YOUR_TAILSCALE_API_KEY>" --env "TAILSCALE_OAUTH_CLIENT_SECRET=<YOUR_TAILSCALE_OAUTH_CLIENT_SECRET>" --transport stdio tailscale-mcp -- npx -y @tailscale-mcp/tailscale-mcpRequires: TAILSCALE_API_KEY (secret), TAILSCALE_OAUTH_CLIENT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of mcp-reconnect publish no settings it asks for, so we do not compare settings.
What it can do: mcp-reconnect · What it can do: Tailscale · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.