Communication

Slack MCP Server

Workspace messages, channels, and collaboration context for team agents.

Install TestedHigh RiskMedium confidencehigh riskclaudecursor

Unranked score draft

Install + docs74
Maintenance65
Auth handling58
Client compatibility72
Real usefulness86
Safety signals49

Evidence history

Review snapshots show why the current score, confidence, and risk labels changed over time.

This review depth is not eligible for MCP Rank leaderboards until a Deep Review is complete.

seed review
DateChangeScoreConfidenceRisk
May 13, 2026
Initial MCP Rank review captured from the curated seed dataset.

The useful surface is obvious and repeatable: channel search, thread reading, and message drafting can materially reduce context switching.

seed snapshot · high risk

69mediumhigh

Evidence notes

The useful surface is obvious and repeatable: channel search, thread reading, and message drafting can materially reduce context switching.
The original MCP reference path is archived, so this review treats provenance as medium confidence even with package and continuation links.
Slack workspace content routinely includes customer names, incident details, credentials pasted by mistake, HR discussions, and private roadmap notes.
The server should be evaluated at the channel and OAuth-scope level, not as one workspace-wide permission decision.
A safer rollout starts with public or low-sensitivity channels and blocks autonomous posting until approval flows are tested.

Best-fit use cases

Best for teams that already have clear channel taxonomy and want agents to summarize public project or incident channels.

Useful for support handoffs when the agent can read a narrow set of channels and produce draft-only responses.

Poor fit for unmanaged workspaces where sensitive data is spread across private channels without retention or access policy.

Risk analysis

The highest risk is data overcollection: a broad workspace token can expose far more context than the user intended.

Posting and reaction tools can create operational noise or make commitments on behalf of people if not gated.

Medium evidence confidence is appropriate because useful public source links exist, but the archived original path weakens maintenance certainty.

Use-case examples

Summarize an incident channel.
Find context from a release discussion.
Draft a follow-up based on a public team channel.