Ext Ops Panel
Open dashboard
Comparison

MCP Slack vs Slack MCP Server

MCP Slack is an MCP server published by crunchtools. Marketplaces we read that list it: 1 (Official MCP Registry). Slack MCP Server is an MCP server published by jtalk22. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceMCP SlackSlack MCP Server
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (PyPI): 423
Downloads/week (PyPI): 223
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 5.1.0
Downloads/month (npm): 2 821
Downloads/week (npm): 1 217
Forks (GitHub): 25
Stars (GitHub): 32
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

MCP Slack vs Slack MCP Server
FactMCP SlackSlack MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)32 (better)
Forks (GitHub) (differs)0 (worse)25 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp-slack-crunchtools)Remote server (mcp.revasserlabs.com/oauth/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/crunchtools/mcp-slackgithub.com/jtalk22/slack-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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 Slack

In its own words, on Official MCP Registry:

Secure read-only MCP server for Slack workspaces

Slack MCP Server

In its own words, on Official MCP Registry:

Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth.

How to run each

MCP Slack As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio slack -- uvx mcp-slack-crunchtools

Slack MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http slack-mcp-server https://mcp.revasserlabs.com/oauth/mcp

Requires: SLACK_COOKIE (secret), SLACK_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Slack MCP Server has a remote endpoint we check. How we check endpoints

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 Slack publish no settings it asks for, so we do not compare settings.

What it can do: MCP Slack · What it can do: Slack MCP Server · Compare two other plugins

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.

Where the data comes from: how the catalog is built