MCP.Market

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

by adelaidasofia·io.github.adelaidasofia/slack-mcp·v0.1.1·1 stars

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

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

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

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

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

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 35% of 1,299 Productivity servers
GitHub stars
1
more than 50% of 854 Productivity servers

Install Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a repository's README, as published. We do not edit it. Read it on GitHub

slack-mcp

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

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

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: listchannels, searchchannels, readchannel, readthread, listusers, searchusers, getuserprofile, search_messages

Write (draft+confirm): sendmessage → confirmsend, sendreplyquote → confirmsend, updateownmessage → confirmsend, cancel_draft

Write (low-consequence, immediate): addreaction, markread, deleteownmessage

Auth modes

Cookie extraction takes ~3 minutes per workspace. See SETUP.md.

Vault auto-export

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

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

Is Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a safe?
Mostly: it is graded B (73/100). Read the Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a safety report
Does Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a need an API key?
Yes. The registry entry asks for SLACK_XOXC_TOKEN.
Is Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v0.1.1.
What can I use instead of Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a?
Servers from other publishers that do the same job: Agent-Native Dispatch MCP server, Trello MCP server and Mirroir MCP server.
How does Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a compare with other Productivity MCP servers?
safety score 73/100 (higher than 35% of 1,299 Productivity servers); github stars 1 (more than 50% of 854 Productivity servers). Full comparison.

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

Same job from other publishers: the closest match first, then the best rated.

  • Agent-Native Dispatch
    Central Slack/Telegram router with jobs, memory, approvals, and A2A delegation
    A
  • Trello
    MCP server for Trello boards with rate limiting, type safety, and comprehensive API integration.
    B
  • Mirroir
    Drive a stock iPhone via iPhone Mirroring: no Developer Mode, Xcode or WDA. LLM-free skill replay.
    C
  • Obsidian Hybrid Search
    Search Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval.
    B
  • Seekstone
    Filesystem-direct Obsidian MCP server — search and edit your vault with low context-tax.
    A

More from adelaidasofia →