Slack MCP vs Discourse MCP

Searches messages, threads, and channel metadata in a Slack workspace, and can post when given a token with write scope On the other side: official stdio server for discourse forums: search topics, read posts, and inspect categories

MCP ServersVerified 2 Nov
Installnpx -y slack-mcp-servernpx -y @discourse/mcp
SourceCommunityOfficial
Deciding factorYou need the recent, informal, thread-level context.versus: You need the durable, searchable, moderator-reviewed answer.
Bottom line

Slack for what was said; Discourse for what was decided.

The short answer

Slack is where decisions happen and disappear; Discourse is where they are kept. An agent reading Slack answers 'what did we say last week' quickly and unreliably. An agent reading a forum answers 'how do we do this' slowly and accurately. Different questions, different indexes.

Facts

OptionInstallSourceLink
Slack MCPnpx -y slack-mcp-serverCommunityRepository ↗
Discourse MCPnpx -y @discourse/mcpOfficialRepository ↗

Pick Slack MCP if

You need the recent, informal, thread-level context.

Pick Discourse MCP if

You need the durable, searchable, moderator-reviewed answer.

What would change our mind

A project going archived, or a maintainer changing the install path, flips this comparison faster than any feature release. Both entries are re-checked weekly, and the date above tells you how much to trust the details.

Read the full entries

More head-to-heads

All comparisons