
Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a
io.github.adelaidasofia由 GitHub 账号 adelaidasofia 发布v0.1.1更新于 Oct 24, 2026
Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, and triple-mode…
概览
本地运行的 Slack MCP 服务器,让助手跨多个工作区读取和搜索消息,并通过草稿加确认流程发送消息。
- 可以做什么
- 列出已配置的 Slack 工作区并做健康检查,响应中令牌会被遮蔽,每次调用写入审计日志。跨工作区读取和搜索频道、话题串、用户与消息。为消息、回复和编辑生成草稿,确认后才发布,也可取消。立即添加表情回应、标记已读、删除助手自己发送的消息。把读取过的频道镜像成本地 Markdown 笔记存入 vault 目录。
- 适用场景
- 适合同时使用多个 Slack 工作区、希望助手搜索和总结对话,或先起草外发消息再由你确认发送的场景。
- 运行要求
- 以本地 Python 进程运行(也可通过 Claude Code 插件安装),需要 .env 文件。每个工作区需要 Slack 令牌:xoxc 加 cookie、xoxp 或 xoxb,其中 SLACK_XOXC_TOKEN 被声明为必填密钥。工作区别名和 vault 路径通过环境变量设置。Cookie 需手动提取,每个工作区约几分钟。
安装
在 SourceWeft 中
- 打开 控制台中的 Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
slack-mcp
[License] [GitHub stars] [Last commit] [Open issues] [PyPI version] [PyPI downloads] [Built by Mycelium AI]
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
Install
Open Claude Code, paste:
Then fill in tokens in .env (see SETUP.md for cookie extraction walkthrough).
Legacy install
Register in your project .mcp.json (or via claude mcp add -s user):
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
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.
来源:README.md,提交 e9c5a02
工具
0版本历史
1- v0.1.1最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分