MCP Slack
Give your agent read-only access to Slack workspace context when implementing features, summarizing threads, or drafting replies from your dev environment.
Overview
io.github.crunchtools/slack is a MCP server for the Build phase that provides secure read-only access to Slack workspace data for agents.
What is this MCP server?
- Secure read-only MCP server for Slack workspaces—limits blast radius versus full post/delete tokens
- mcp-slack-crunchtools on PyPI with stdio transport at version 0.1.2
- Pull channel and message context into Claude Code or Cursor without exporting Slack manually
- Model Context Protocol server schema 2025-12-11 manifest
- Read-only by design: suited for context gathering, not autonomous spammy posting
- Server version 0.1.2
- PyPI identifier mcp-slack-crunchtools
- Transport type stdio
Community signal: 1 GitHub stars.
What problem does it solve?
Critical decisions and bug reports sit in Slack threads your agent cannot read, so you retype context every time you code or document.
Who is it for?
Solo builders who live in Slack for user feedback and team chat but want read-only MCP context inside Claude Code or Cursor.
Skip if: Workflows that require the agent to post messages autonomously, or teams that prohibit Slack API access for agents.
What do I get? / Deliverables
After MCP setup, the agent can pull read-only Slack workspace context while you build integrations and respond with accurate thread awareness.
- Configured read-only Slack MCP server in your agent
- In-session access to Slack workspace context exposed by server tools
Recommended MCP Servers
Journey fit
Slack MCP wiring is Build-phase agent tooling: you integrate a communication surface into the stack where you code and automate. Integrations is the shelf for third-party workspace connectors such as read-only Slack MCP servers.
How it compares
Read-only Slack MCP connector, not a Slack bot builder skill or full write-capable chat automation suite.
Common Questions / FAQ
Who is io.github.crunchtools/slack for?
Indie developers and small teams using Slack who want MCP agents to read workspace context safely without write permissions.
When should I use io.github.crunchtools/slack?
During Build integrations work when you need channel or message context from Slack while implementing fixes, specs, or support drafts.
How do I add io.github.crunchtools/slack to my agent?
Install mcp-slack-crunchtools from PyPI, configure stdio in your MCP client, and complete Slack app or token setup as documented in github.com/crunchtools/mcp-slack.