Ext Ops Panel
Open dashboard
Comparison

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a vs Tailscale

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a is an MCP server published by adelaidasofia. Marketplaces we read that list it: 2 (Official MCP Registry, 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-11-11. 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

Where each is published
MarketplaceMulti-workspace Slack MCP server with draft+confirm safety, vault auto-export, aTailscale
Official MCP Registry Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 2.0.5
Downloads/month (npm): 1 641
Downloads/week (npm): 531
Forks (GitHub): 3
Stars (GitHub): 19
Not marked · First seen
Claude Code: claude-plugins-community Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
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): 19
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

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a vs Tailscale
FactMulti-workspace Slack MCP server with draft+confirm safety, vault auto-export, aTailscale
Marketplaces that list it22
Stars (GitHub) (differs)2 (worse)19 (better)
Forks (GitHub) (differs)0 (worse)3 (better)
Last release (differs)Not published2026-10-26
Where it runs (differs)On your machine (https://github.com/adelaidasofia/slack-mcp/releases/download/v0.1.1/slack-mcp.mcpb)On your machine (@tailscale-mcp/tailscale-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 17, secrets among them: 2
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/adelaidasofia/slack-mcpgithub.com/tailscale-mcp/tailscale-mcp
Changes in the last 7 days00
First seen2026-10-112026-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

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a

In its own words, on Official MCP Registry:

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, and triple-mode…

Tailscale

In its own words, on Official MCP Registry:

Drive a Tailscale node and its tailnet through the CLI and the control-plane API

How to run each

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install slack-mcp@claude-community

Requires: SLACK_XOXC_TOKEN (secret)

Tailscale As a local MCP server: npm package

Claude Code
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-mcp

Requires: 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

Only Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a asks for

  • SLACK_XOXC_TOKEN (secret)

Only Tailscale asks for

  • TAILSCALE_API_KEY (secret)
  • TAILSCALE_MCP_ALLOW_DESTRUCTIVE
  • TAILSCALE_MCP_ALLOW_WRITE
  • TAILSCALE_MCP_PRESET
  • TAILSCALE_OAUTH_CLIENT_ID
  • TAILSCALE_OAUTH_CLIENT_SECRET (secret)
  • TAILSCALE_TAILNET

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a · What it can do: Tailscale · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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.

Where the data comes from: how the catalog is built