MCP Slack

io.github.crunchtools由 GitHub 帳號 crunchtools 發布v0.1.2更新於 Oct 24, 2026

Secure read-only MCP server for Slack workspaces

已驗證STDIO僅桌面溝通與協作

概覽

AI 產生的概覽

透過 MCP 用戶端讀取 Slack 頻道、訊息、使用者與檔案，並可排程或傳送訊息。

可以做什麼
一個本機 MCP 伺服器，讓助理讀取 Slack 工作區：列出頻道、讀取頻道歷史與討論串回覆、搜尋訊息，查看表情回應、星號標記、使用者、個人資料與檔案中繼資料。兩個寫入工具可依可設定的延遲排程訊息或立即張貼，並可取消已排程的訊息。它直接以 HTTP 與 Slack 通訊，不依賴 SDK。
適用情境
適合助理需要在 Slack 中查資料時，例如近期頻道動態、某個討論串、某個人或某個檔案，或傳送一則帶有短暫取消窗口的訊息。它不用於編輯或刪除 Slack 中既有的內容。
執行需求
以本機 Python 套件（uvx 或 uv）或容器方式執行。需要兩種互斥認證之一：SLACK_USER_TOKEN（來自 Slack 應用程式的使用者 OAuth 權杖），或 cookie 組合 SLACK_COOKIE_TOKEN 與 SLACK_COOKIE_D。選用的 SLACK_ADD_MESSAGE_DELAY 控制訊息排程。需要連線至 Slack 的網路。
安裝前請注意
cookie 模式使用即時瀏覽器工作階段認證（SLACK_COOKIE_TOKEN、SLACK_COOKIE_D），持有者可完整以該使用者身分在 Slack 中操作；它們會隨瀏覽器工作階段過期，Slack 也可能隨時使其失效。在能安裝 Slack 應用程式時應優先使用 SLACK_USER_TOKEN。兩個寫入工具會傳送或取消訊息，需要 chat:write 權限；訊息預設延後傳送，留有取消窗口。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 MCP Slack，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

mcp-slack-crunchtools

Secure MCP server for Slack workspaces. Provides Claude Code (and other MCP clients) with read access to your Slack channels, messages, users, and files, and can send a message on your behalf.

Features

  • Mostly read: 15 of the 17 tools only read and publish readOnlyHint: true. The other two send a message and cancel a scheduled one; nothing edits or deletes existing content.
  • Secure: 6-layer security model (input validation, token handling, client hardening, output sanitization, runtime protection, supply chain security).
  • User OAuth Token: Uses xoxp- tokens for user-scoped access to your workspace.
  • No SDK dependency: Uses httpx directly for minimal, auditable HTTP calls.

Quick Start

Using uvx (Recommended)

bash
claude mcp add mcp-slack-crunchtools \    --env SLACK_USER_TOKEN=xoxp-your-token \    -- uvx mcp-slack-crunchtools

Using Container

bash
claude mcp add mcp-slack-crunchtools \    --env SLACK_USER_TOKEN=xoxp-your-token \    -- podman run -i --rm -e SLACK_USER_TOKEN quay.io/crunchtools/mcp-slack

Local Development

bash
claude mcp add mcp-slack-crunchtools \    --env SLACK_USER_TOKEN=xoxp-your-token \    -- uv run mcp-slack-crunchtools

Setup

See CLAUDE.md for detailed instructions on creating a Slack app and obtaining a User OAuth Token.

Configuration

Authentication uses one of two mutually exclusive modes. The server picks cookie mode when both cookie variables are set, and token mode otherwise.

VariableRequiredDefaultDescription
SLACK_USER_TOKENtoken mode—User OAuth token (xoxp-...) from a Slack app installed in the workspace.
SLACK_COOKIE_TOKENcookie mode—Browser session token (xoxc-...). Must be paired with SLACK_COOKIE_D.
SLACK_COOKIE_Dcookie mode—Value of the d cookie (xoxd-...) from the same browser session. Sent as a Cookie: header alongside SLACK_COOKIE_TOKEN.
SLACK_ADD_MESSAGE_DELAYno3mHow far ahead outgoing messages are scheduled, giving you a window to cancel one. Duration string: 30s, 5m, 2h, or a bare integer for seconds. Set to 0, 0s, none, or false to disable scheduling and post immediately.

Which auth mode to use

Cookie mode is the working path for this deployment. Token mode requires a Slack app to be created and approved in the workspace; where that approval is not available, cookie mode is the only way to authenticate at all.

Cookie mode borrows an existing browser session rather than holding a credential issued to an application. That has consequences worth stating plainly:

  • Both values are live session credentials. Anything holding them can act as you in Slack, with your full access. Treat them exactly as you would your password.
  • They expire when the browser session does, so cookie mode needs periodic re-extraction. A sudden wave of auth failures usually means the session rotated, not that the server broke.
  • Slack does not issue these for programmatic use and can invalidate them at any time. Cookie mode is a workaround for the absence of an approved app, not a supported integration path.

Prefer SLACK_USER_TOKEN whenever a Slack app can actually be installed.

Tools

ToolDescription
slack_auth_testTest connection and get token owner info
slack_list_channelsList workspace channels
slack_get_channel_infoGet channel details
slack_get_channel_historyRead channel messages
slack_get_thread_repliesRead thread replies
slack_list_channel_membersList channel members
slack_search_messagesSearch messages
slack_get_reactionsGet message reactions
slack_list_reactionsList user's reactions
slack_list_starsList starred items
slack_get_user_infoGet user details
slack_list_usersList workspace members
slack_get_user_profileGet user profile
slack_list_filesList files (metadata only)
slack_get_file_infoGet file metadata
slack_send_messageSchedule a message SLACK_ADD_MESSAGE_DELAY ahead, or post it immediately when the delay is 0 (write)
slack_cancel_scheduled_messageCancel a scheduled message before it sends (write)

The two write tools need the chat:write scope in token mode.

Security

See SECURITY.md for the full security design document.

License

AGPL-3.0-or-later

來源：README.md，提交 7e2131d

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

1
  1. v0.1.2最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分