Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

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

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

adelaidasofia/slack-mcp
1 starsMITUpdated 2026-06-22Community

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

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

README.md

slack-mcp

<!-- mycelium-badges:start -->

<p> <a href="https://github.com/adelaidasofia/slack-mcp/blob/main/LICENSE"><img alt="License" src="https://img.shields.io/github/license/adelaidasofia/slack-mcp?color=blue"></a> <a href="https://github.com/adelaidasofia/slack-mcp/stargazers"><img alt="GitHub stars" src="https://img.shields.io/github/stars/adelaidasofia/slack-mcp?color=eab308"></a> <a href="https://github.com/adelaidasofia/slack-mcp/commits/main"><img alt="Last commit" src="https://img.shields.io/github/last-commit/adelaidasofia/slack-mcp"></a> <a href="https://github.com/adelaidasofia/slack-mcp/issues"><img alt="Open issues" src="https://img.shields.io/github/issues/adelaidasofia/slack-mcp"></a> <a href="https://pypi.org/project/adelaidasofia-slack-mcp/"><img alt="PyPI version" src="https://img.shields.io/pypi/v/adelaidasofia-slack-mcp?color=blue&label=pypi"></a> <a href="https://pypi.org/project/adelaidasofia-slack-mcp/"><img alt="PyPI downloads" src="https://img.shields.io/pypi/dm/adelaidasofia-slack-mcp?color=blue&label=downloads"></a> <a href="https://myceliumai.co"><img alt="Built by Mycelium AI" src="https://img.shields.io/badge/built_by-Mycelium_AI-15B89A"></a> </p>

<!-- mycelium-badges:end -->

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).

<details> <summary>Legacy install</summary>

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.

</details>

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_messageconfirm_send, send_reply_quoteconfirm_send, update_own_messageconfirm_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 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_EXPORTtrue/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_INJECTIONtrue/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.

Related MCPs

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.

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Communication servers.