Ext Ops Panel
Open dashboard
Comparison

io.github.chrischall/microsoft-teams-mcp vs Slack

io.github.chrischall/microsoft-teams-mcp is an MCP server published by chrischall. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Slack is an MCP server published by mindstone. 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
Marketplaceio.github.chrischall/microsoft-teams-mcpSlack
Official MCP Registry Listed
Version: 0.7.0
Downloads/month (npm): 2 769
Downloads/week (npm): 497
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.3.0
Downloads/month (npm): 3 929
Downloads/week (npm): 520
Forks (GitHub): 4
Stars (GitHub): 13
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.7.0
Downloads/month (npm): 2 769
Downloads/week (npm): 497
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed

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

io.github.chrischall/microsoft-teams-mcp vs Slack
Factio.github.chrischall/microsoft-teams-mcpSlack
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)0 (worse)13 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last release (differs)2026-10-20Not published
Where it runs (differs)On your machine (@chrischall/microsoft-teams-mcp)On your machine (@mindstone/mcp-server-slack)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)18, secrets among them: 28, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/chrischall/microsoft-teams-mcpgithub.com/mindstone/mcp-servers
Changes in the last 7 days (differs)30
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

io.github.chrischall/microsoft-teams-mcp

In its own words, on Official MCP Registry:

Microsoft Teams for Claude — read any chat or channel and its unread messages; send and react

Slack

In its own words, on Official MCP Registry:

Slack MCP server: channels, messages, threads, reactions, users, files, and scheduled messages

How to run each

io.github.chrischall/microsoft-teams-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "MCP_CONFIRM_SECRET=<YOUR_MCP_CONFIRM_SECRET>" --env "TEAMS_ACCESS_TOKEN=<YOUR_TEAMS_ACCESS_TOKEN>" --transport stdio microsoft-teams-mcp -- npx -y @chrischall/microsoft-teams-mcp

Requires: MCP_CONFIRM_SECRET (secret), TEAMS_ACCESS_TOKEN (secret)

Slack As a local MCP server: npm package

Claude Code
claude mcp add --env "SLACK_CLIENT_SECRET=<YOUR_SLACK_CLIENT_SECRET>" --env "SLACK_CONFIG_PATH=<YOUR_SLACK_CONFIG_PATH>" --env "SLACK_TEAM_ID=<YOUR_SLACK_TEAM_ID>" --transport stdio mcp-server-slack -- npx -y @mindstone/mcp-server-slack

Requires: SLACK_CLIENT_SECRET (secret), SLACK_CONFIG_PATH, SLACK_TEAM_ID

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 io.github.chrischall/microsoft-teams-mcp asks for

  • FETCHPROXY_IDENTITY_DIR
  • FETCHPROXY_WS_HOST
  • MCP_CONFIRM_ELICITATION
  • MCP_CONFIRM_MODE
  • MCP_CONFIRM_SECRET (secret)
  • MCP_CONFIRM_TTL_SECONDS
  • TEAMS_ACCESS_TOKEN (secret)
  • TEAMS_CAPTURE_TIMEOUT
  • TEAMS_CHATSVC_BASE
  • TEAMS_CHATSVC_REGION
  • TEAMS_DISABLE_FETCHPROXY
  • TEAMS_OUTPUT_DIR
Show the remaining 6
  • TEAMS_SHAREPOINT_TOKEN_FILE
  • TEAMS_SUBSTRATE_TOKEN_FILE
  • TEAMS_TIME_ZONE
  • TEAMS_TOKEN_CACHE
  • TEAMS_TOKEN_FILE
  • TEAMS_WS_PORT

Only Slack asks for

  • MCP_WORKSPACE_PATH
  • SLACK_CLIENT_ID
  • SLACK_CLIENT_SECRET (secret)
  • SLACK_CONFIG_PATH
  • SLACK_DISABLE_REFRESH
  • SLACK_MAX_RETRIES
  • SLACK_REQUEST_TIMEOUT_MS
  • SLACK_TEAM_ID

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

What it can do: io.github.chrischall/microsoft-teams-mcp · What it can do: Slack · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. 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