Slack
Connect your agent to Slack to read channels, post updates, manage threads, and add reactions for support and ops loops.
Overview
com.pulsemcp/slack is a MCP server for the Grow phase that lets your agent read and write Slack messages, threads, and reactions in your workspace.
What is this MCP server?
- stdio MCP package slack-workspace-mcp-server v0.0.6 via npx
- Read and write Slack messages with thread management and reactions
- SLACK_BOT_TOKEN (xoxb-) required for workspace access
- ENABLED_TOOLGROUPS comma list toggles readonly vs write tool groups
- Experimental package from pulsemcp/mcp-servers Slack subfolder
- Server schema version 0.0.6
- Package identifier slack-workspace-mcp-server
- ENABLED_TOOLGROUPS values documented: readonly, write
Community signal: 70 GitHub stars.
What problem does it solve?
Context switching between your IDE and Slack breaks flow when you need quick thread summaries, replies, or launch updates.
Who is it for?
Indie builders who run support and launch comms in Slack and want agent-assisted drafting and thread management.
Skip if: Organizations that require enterprise Slack governance, eDiscovery, or complex multi-workspace apps without careful token scoping.
What do I get? / Deliverables
After you add a bot token and optional tool-group limits, your agent can operate Slack channels from MCP with controlled read/write scope.
- Agent-callable Slack read and/or write tools per ENABLED_TOOLGROUPS
- Thread and reaction operations without leaving the coding agent
Recommended MCP Servers
Journey fit
Slack bridges product work and user-facing support once you are shipping and need fast human-in-the-loop communication. Support is the canonical shelf for message read/write tooling that keeps founders responsive without leaving the IDE.
How it compares
Slack workspace MCP bridge, not a CRM or ticketing replacement skill.
Common Questions / FAQ
Who is com.pulsemcp/slack for?
Solo founders and small teams using Slack for users and ops who want Claude Code, Cursor, or similar agents inside those conversations.
When should I use com.pulsemcp/slack?
Use it when you are handling support threads, posting ship notes, or automating routine Slack updates after your product is live.
How do I add com.pulsemcp/slack to my agent?
Create a Slack app with a bot token (xoxb-), add slack-workspace-mcp-server via npx stdio config, set SLACK_BOT_TOKEN, optionally ENABLED_TOOLGROUPS, then restart MCP.