Ext Ops Panel
Open dashboard
Comparison

Slack (Archived) vs ZulipChat MCP Server

Slack (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). ZulipChat MCP Server is an MCP server published by akougkas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplaceSlack (Archived)ZulipChat MCP Server
Docker MCP Catalog Listed
Version: sha256:4cc10c3f4bd9
Forks (GitHub): 11 793
Pulls (Docker Hub): 312 700
Stars (Docker Hub): 25
Stars (GitHub): 91 324
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.2
Downloads/month (PyPI): 813
Downloads/week (PyPI): 611
Forks (GitHub): 16
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

Slack (Archived) vs ZulipChat MCP Server
FactSlack (Archived)ZulipChat MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)91 324 (better)32 (worse)
Pulls (Docker Hub) (differs)312 700No figure on Docker Hub
Forks (GitHub) (differs)11 793 (better)16 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/slack)On your machine (zulipchat-mcp)
Transportstdiostdio
Tools it declares (differs)8Not published
Environment variables it asks for3, secrets among them: 13, secrets among them: 1
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/akougkas/zulipchat-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

Slack (Archived)

In its own words, on Docker MCP Catalog:

Interact with Slack Workspaces over the Slack API.

ZulipChat MCP Server

In its own words, on Official MCP Registry:

ZulipChat MCP: Connect AI to Zulip with 60+ tools for messaging, streams, events, and analytics

How to run each

Slack (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --env "SLACK_BOT_TOKEN=<YOUR_SLACK_BOT_TOKEN>" --transport stdio slack -- docker run -i --rm -e SLACK_BOT_TOKEN mcp/slack

Requires: SLACK_BOT_TOKEN (secret)

ZulipChat MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ZULIP_API_KEY=<YOUR_ZULIP_API_KEY>" --transport stdio zulipchat -- uvx zulipchat-mcp

Requires: ZULIP_API_KEY (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 ZulipChat MCP Server 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_IDS
  • SLACK_TEAM_ID

Only ZulipChat MCP Server asks for

  • ZULIP_API_KEY (secret)
  • ZULIP_EMAIL
  • ZULIP_SITE

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

What it can do: Slack (Archived) · What it can do: ZulipChat MCP Server · 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.

Where the data comes from: how the catalog is built