Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a

Registre officiel Productivité

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, and triple-mode…

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

MCPB package https://github.com/adelaidasofia/slack-mcp/releases/download/v0.1.1/slack-mcp.mcpb

Variables d'environnement

  • SLACK_XOXC_TOKEN obligatoire secret Extracted via browser dev tools (or xoxb for bot auth)

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. slack-mcp
  2. Why use this over the alternatives
  3. Install
  4. Tools (v0.1.1)
  5. Auth modes
  6. Vault auto-export
  7. Configuration
  8. Safety patterns
  9. Related MCPs
  10. Telemetry
  11. License

slack-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

ThisAnthropic connectorkorotovsky/slack-mcp-server
Multi-workspace per serverYesNoNo
Draft + confirm on writesYesNoNo
Vault auto-export of readsYesNoNo
Prompt-injection scrubberYesNoNo
Audit logYesNoNo
xoxc / xoxp / xoxb authYesn/aYes
StatusActiveActive (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

ModeToken shapeCapabilityWhen to use
xoxcxoxc-... + xoxd-... cookieFull (search, internal APIs)Default. Best for personal use across multiple workspaces.
xoxpxoxp-...Permanent, OAuth, search restricted on free plansIf you don't want occasional cookie re-extraction.
xoxbxoxb-...Bot-only, no search, invited channels onlyRare. 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 omit workspace
  • 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 (default true)
  • SLACK_MCP_AUDIT_LOG_PATH — JSONL audit log path
  • SLACK_MCP_DRAFT_TTL_SECONDS — draft expiration (default 3600)
  • SLACK_MCP_SCRUB_PROMPT_INJECTION — true/false (default true)

Safety patterns

  • Draft + confirm. Every send (send_message, send_reply_quote, update_own_message) returns a draft_id. Nothing posts until confirm_send(draft_id) is called. Drafts expire after 1 hour. One-time confirm. update_own_message drafts 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 workspace to 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_workspaces returns redacted profiles only. Tokens never appear in tool responses.

Same author, same architecture pattern (FastMCP, draft+confirm on writes where applicable, vault auto-export, MIT):

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.

Questions fréquentes

Qu'est-ce que Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a ?

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, and triple-mode…

Comment installer Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a ?

Suivez les étapes d'installation de sa documentation, affichée sur cette page et dans son dépôt.

Faut-il une clé API pour Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a ?

Oui. Il attend SLACK_XOXC_TOKEN, à renseigner dans sa configuration.

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a ?

Il est publié par adelaidasofia. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.