Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI builders, IT admins, and platform engineers who need a clean MCP bridge between a coding agent and a real Slack workspace, because korotovsky/slack-mcp-server ships the full DMs/channels/Apps surface with GovSlack support and no per-channel permission prompts, which means an agent can read and act on Slack without the OAuth token-by-token approval loop that makes other Slack integrat
Who should use it
Who should skip it
Skip or sandbox it if you cannot review permissions, data access, and failure modes before use.
Risk explanation
It exposes the full Slack surface (DMs, channels, Apps, GovSlack) via MCP, so audit the workspace-token scope, lock the server down to the channels the agent actually needs, and never point it at a production or GovSlack workspace without a manual review step in front of any message-send action.