Ext Ops Panel
Open dashboard
Comparison

com.pulsemcp/slack vs io.github.mrfentmen/slack-mcp

com.pulsemcp/slack is an MCP server published by pulsemcp.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mrfentmen/slack-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
Marketplacecom.pulsemcp/slackio.github.mrfentmen/slack-mcp
Official MCP Registry Listed
Version: 0.0.7
Downloads/month (npm): 2 738
Downloads/week (npm): 328
Forks (GitHub): 10
Stars (GitHub): 81
Not marked · First seen
Listed
Version: 1.1.0
Downloads/month (npm): 730
Downloads/week (npm): 72
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

com.pulsemcp/slack vs io.github.mrfentmen/slack-mcp
Factcom.pulsemcp/slackio.github.mrfentmen/slack-mcp
Marketplaces that list it11
Stars (GitHub) (differs)81No figure on GitHub
Forks (GitHub) (differs)10No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (slack-workspace-mcp-server)On your machine (@mrfentmen/slack-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/pulsemcp/mcp-serversgithub.com/mrfentmen/premium-mcps
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-17

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

com.pulsemcp/slack

In its own words, on Official MCP Registry:

MCP server for Slack — read/write messages, manage threads, and react to messages.

io.github.mrfentmen/slack-mcp

In its own words, on Official MCP Registry:

Query the Slack Web API (bot token; set SLACK_BOT_TOKEN, xoxb): channels, history, post messages.

How to run each

com.pulsemcp/slack As a local MCP server: npm package

Claude Code
claude mcp add --env "SLACK_BOT_TOKEN=<YOUR_SLACK_BOT_TOKEN>" --transport stdio slack -- npx -y slack-workspace-mcp-server

Requires: SLACK_BOT_TOKEN (secret)

io.github.mrfentmen/slack-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio slack-mcp -- npx -y @mrfentmen/slack-mcp

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 io.github.mrfentmen/slack-mcp publish no settings it asks for, so we do not compare settings.

What it can do: com.pulsemcp/slack · What it can do: io.github.mrfentmen/slack-mcp · 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