Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a
LocalAbout Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a
A Slack MCP server for working across multiple workspaces, with three authentication modes. It combines draft-and-confirm safeguards for consequential writes with read exports to a vault.
Key features
- 01Route operations across Slack workspaces
- 02Read channels, threads, users, and messages
- 03Draft and confirm message sends and edits
- 04Export read channels to a vault
- 05Log calls and redact tokens
- 06Scrub known prompt-injection patterns
Use cases
- 01Search messages across configured workspaces
- 02Review a channel and save its contents to a vault
- 03Prepare a message or edit for confirmation
- 04Limit accidental posts to the wrong workspace
MCP support
Exposes Slack read and write tools to MCP clients. Message sends, quoted replies, and edits require a separate confirmation call; write tools require a workspace parameter.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEslack-mcp
Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, and triple-mode auth.
One process, N workspaces, every write goes through draft → confirm. Built because the existing Slack MCP servers are single-workspace per instance and the Anthropic reference impl was deprecated.
Why use this over the alternatives
| This | Anthropic connector | korotovsky/slack-mcp-server | |
|---|---|---|---|
| Multi-workspace per server | Yes | No | No |
| Draft + confirm on writes | Yes | No | No |
| Vault auto-export of reads | Yes | No | No |
| Prompt-injection scrubber | Yes | No | No |
| Audit log | Yes | No | No |
| xoxc / xoxp / xoxb auth | Yes | n/a | Yes |
| Status | Active | Active (limited) | Active |
Install
Open Claude Code, paste:
/plugin marketplace add adelaidasofia/slack-mcp
/plugin install slack-mcp@slack-mcp
Then fill in tokens in .env (see SETUP.md for cookie extraction walkthrough).
Legacy install
git clone https://github.com/adelaidasofia/slack-mcp.git ~/.claude/slack-mcp
cd ~/.claude/slack-mcp
pip3 install --break-system-packages -r requirements.txt
cp .env.example .env
# fill in tokens — see SETUP.md for cookie extraction walkthrough
Register in your project .mcp.json (or via claude mcp add -s user):
{
"mcpServers": {
"slack": {
"command": "python3",
"args": ["-m", "slack_mcp.server"],
"cwd": "/Users/YOU/.claude/slack-mcp"
}
}
}
Restart Claude Code, then run claude mcp list to verify slack shows up.
Tools (v0.1.1)
Meta: list_workspaces, healthcheck
Read: list_channels, search_channels, read_channel, read_thread, list_users, search_users, get_user_profile, search_messages
Write (draft+confirm): send_message → confirm_send, send_reply_quote → confirm_send, update_own_message → confirm_send, cancel_draft
Write (low-consequence, immediate): add_reaction, mark_read, delete_own_message
Auth modes
| Mode | Token shape | Capability | When to use |
|---|---|---|---|
xoxc | xoxc-... + xoxd-... cookie | Full (search, internal APIs) | Default. Best for personal use across multiple workspaces. |
xoxp | xoxp-... | Permanent, OAuth, search restricted on free plans | If you don't want occasional cookie re-extraction. |
xoxb | xoxb-... | Bot-only, no search, invited channels only | Rare. Use only when you want bot semantics. |
Cookie extraction takes ~3 minutes per workspace. See SETUP.md.
Vault auto-export
Every read_channel call mirrors the channel to <vault>/🤖 AI Chats/Slack/<workspace>/<channel>.md. Idempotent (same channel + day overwrites cleanly). Disable via SLACK_MCP_VAULT_EXPORT=false.
Configuration
All config via env vars (loaded from .env at process start):
SLACK_WORKSPACES— comma-separated list of aliases (e.g.onde,mycelium)SLACK_PRIMARY_WORKSPACE— default workspace when tool calls omitworkspace- Per-workspace:
SLACK_WORKSPACE_<ALIAS>_TYPE,_TOKEN,_COOKIE(xoxc only),_TEAM_ID,_LABEL SLACK_MCP_VAULT_PATH— vault root for the auto-export mirror (default~/Documents/Vault)SLACK_MCP_VAULT_EXPORT—true/false(defaulttrue)SLACK_MCP_AUDIT_LOG_PATH— JSONL audit log pathSLACK_MCP_DRAFT_TTL_SECONDS— draft expiration (default 3600)SLACK_MCP_SCRUB_PROMPT_INJECTION—true/false(defaulttrue)
Safety patterns
- Draft + confirm. Every send (
send_message,send_reply_quote,update_own_message) returns adraft_id. Nothing posts untilconfirm_send(draft_id)is called. Drafts expire after 1 hour. One-time confirm.update_own_messagedrafts include a before/after preview so the operator can diff before confirming the edit. - Workspace required on writes. No global default for sends — every write tool requires
workspaceto prevent wrong-workspace posts when channel names collide. - Audit log. Every tool call appends a JSONL record. Tokens are redacted.
- Prompt-injection scrubber. Incoming message text is sanitized for known prompt-injection patterns (zalgo, role-spoof headers, fake fences). Hits are wrapped not deleted so the operator sees the attempt.
- Token redaction.
list_workspacesreturns redacted profiles only. Tokens never appear in tool responses.
Related MCPs
Same author, same architecture pattern (FastMCP, draft+confirm on writes where applicable, vault auto-export, MIT):
- imessage-mcp - macOS iMessage
- whatsapp-mcp - WhatsApp via whatsmeow
- google-workspace-mcp - Gmail / Calendar / Drive / Docs / Sheets
- apollo-mcp - Apollo.io CRM + sequences
- substack-mcp - Substack writing + analytics
- luma-mcp - lu.ma events
- parse-mcp - markitdown / Docling / LlamaParse router
- rescuetime-mcp - RescueTime productivity data
- graph-query-mcp - vault knowledge graph queries
- investor-relations-mcp - seed-raise pipeline tracker
- vault-sync-mcp - bidirectional vault sync
Telemetry
This plugin sends a single anonymous install signal to myceliumai.co the first time it loads in a Claude Code session on a given machine.
What is sent:
- Plugin name (e.g.
slack-mcp) - Plugin version (e.g.
0.1.0)
What is NOT sent:
- No user identifiers, names, emails, tokens, or API keys
- No file paths, message content, or anything from your work
- No IP address is stored after dedup processing
Why: Helps the maintainer know which plugins people actually install, so attention goes to the ones that get used.
Opt out: Set the environment variable MYCELIUM_NO_PING=1 before launching Claude Code. The hook will skip the network call entirely. Already-pinged installs leave a sentinel at ~/.mycelium/onboarded-<plugin> — delete it if you want to reset state.
License
MIT — see LICENSE.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.