Multi Workspace Slack MCP Server With Draft+Confirm Safety, Vault Auto Export, A
Connect multi-workspace Slack to your agent with draft-and-confirm sends, vault exports, and flexible auth modes so ops messages stay safe.
Overview
slack-mcp is a MCP server for the Build phase that connects multi-workspace Slack with draft-confirm safety, vault export, and multiple operating modes for agents.
What is this MCP server?
- Multi-workspace Slack support in one MCP server (v0.1.1)
- Draft-plus-confirm flow reduces accidental channel posts from agents
- Vault auto-export for durable copies of drafted or sent content
- Triple-mode operation described in catalog title for auth/workspace flexibility
- SLACK_XOXC_TOKEN (or xoxb bot token) via browser devtools extraction
- Published server version 0.1.1 with stdio .mcpb distribution
- 1 required secret environment variable: SLACK_XOXC_TOKEN (or xoxb alternative)
- Catalog highlights 3 operational themes: multi-workspace, draft+confirm safety, vault auto-export (triple-mode auth/oper
Community signal: 1 GitHub stars.
What problem does it solve?
Solo builders want agents in Slack but fear irreversible posts and scattered workspace tokens across side projects.
Who is it for?
Indie operators who live in Slack for users and partners and need MCP access with explicit send confirmation and export.
Skip if: Builders who want read-only search with enterprise SSO governance—this is a pragmatic token-based indie integration.
What do I get? / Deliverables
After you configure slack-mcp, your agent can draft, confirm, and archive Slack actions across workspaces instead of firing blind API calls.
- Agent tools for Slack read/write flows with draft-and-confirm sending
- Vault auto-export copies of messaging workflows for your records
- Multi-workspace coverage from a single MCP registration
Recommended MCP Servers
Journey fit
Slack wiring is a Build integration you add while shipping agent tooling and customer-facing workflows, even if you also use it in Grow for support. Integrations captures third-party messaging APIs, tokens, and safety gates rather than pure frontend or backend app code.
How it compares
Guarded Slack communication MCP, not a generic webhook skill or email marketing connector.
Common Questions / FAQ
Who is slack-mcp for?
Solo builders and small teams using Claude Code or Cursor who manage more than one Slack workspace and want safer agent-driven messaging.
When should I use slack-mcp?
Use it during Build and early Grow when you integrate launch updates, support drafts, or internal ops bots that must not post without confirmation.
How do I add slack-mcp to my agent?
Extract SLACK_XOXC_TOKEN or a bot xoxb token per Slack’s guidance, install slack-mcp v0.1.1 .mcpb, configure stdio MCP env secrets, and enable tools in your host.