Slack (Archived) vs com.mambabuilt/mcp-threads-keyword-search
Slack (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.mambabuilt/mcp-threads-keyword-search is an MCP server published by mambabuilt.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |   Slack (Archived) |  com.mambabuilt/mcp-threads-keyword-search |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:4cc10c3f4bd9 Forks (GitHub): 11 931 Pulls (Docker Hub): 314 945 Stars (Docker Hub): 25 Stars (GitHub): 91 873 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 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 | Slack (Archived) | com.mambabuilt/mcp-threads-keyword-search |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 873 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 314 945 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 931 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-05 |
| Where it runs (differs) | On your machine (mcp/slack) | On your machine (@mambalabsdev/mcp-threads-keyword-search) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/mambalabsdev/mcp-threads-keyword-search |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-11-01 |
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
Slack (Archived)
Interact with Slack Workspaces over the Slack API.
com.mambabuilt/mcp-threads-keyword-search
Threads posts by keyword with exact phrase matching, author, date, likes, and link, no login
How to run each
Slack (Archived) As a local MCP server: Docker image
claude mcp add --env "SLACK_BOT_TOKEN=<YOUR_SLACK_BOT_TOKEN>" --transport stdio slack -- docker run -i --rm -e SLACK_BOT_TOKEN mcp/slackRequires: SLACK_BOT_TOKEN (secret)
com.mambabuilt/mcp-threads-keyword-search As a local MCP server: npm package
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio mcp-threads-keyword-search -- npx -y @mambalabsdev/mcp-threads-keyword-searchRequires: APIFY_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of com.mambabuilt/mcp-threads-keyword-search publish no list of tools, so we do not compare tools.
Settings each asks for
Only Slack (Archived) asks for
SLACK_BOT_TOKEN (secret)SLACK_CHANNEL_IDSSLACK_TEAM_ID
Only com.mambabuilt/mcp-threads-keyword-search asks for
APIFY_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Slack (Archived) · What it can do: com.mambabuilt/mcp-threads-keyword-search · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.