← MCP

Slack MCP ServerSlack MCP Server

Slack（Salesforce）

MCPMCP 协作Collaboration 消息Messaging 远程托管Remote-hosted OAuthOAuth admin审批Admin approval partial lifecycle: active 核验Checked 2026-10-30

Slack 自营的官方 MCP server（mcp.slack.com/mcp）：agent 能搜工作区、读线程、代拟消息、管 canvas 与 Lists。两条硬口径：admin 审批是前置门；它只在会话里响应，不监视不触发。诚实标注：旧 slackapi 仓已 404；reference 版已归档转第三方维护——本条目是 Slack 自营线。

Slack's self-hosted official MCP server (mcp.slack.com/mcp): agents search the workspace, read threads, draft messages, manage canvases and Lists. Two hard facts: admin approval is a front gate; it only answers inside a session — no watching, no triggers. The old slackapi repo 404s; the reference version was archived to a third party.

适合与不适合When to use it, when not to

适合：让 agent 拿「团队真实讨论」作上下文、频道总结、代拟消息草稿。不适合：事件触发自动化（那是 Workflow 线的活）；要 bot-token 直连的旧路线。

Fits: agents grounding answers in real team discussions, channel summaries, drafted messages. Not a fit: event-triggered automation (that is the Workflow line); old bot-token direct routes.

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-21

出品属地Origin: 国外出品foreign-made　Slack Technologies（Salesforce 旗下，美国）。Slack Technologies (a Salesforce company, US).
国内使用Direct access: 大陆可直连direct OK　docs.slack.dev 直连实测 200（2026-10-21）；mcp.slack.com 端点直连未单独测——大陆可达性未逐条核验。docs.slack.dev measured 200 direct (2026-10-21); the mcp.slack.com endpoint was not individually measured for mainland reachability.
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-21 检索）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-21); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

11 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: 它自己不调模型——被 MCP 客户端调用的接口实现。它把 Slack 工作区能力（搜索、读消息/线程、发消息、canvases、Lists）包装成工具给 agent 用。
It calls no model itself — an interface implementation called by MCP clients. It wraps Slack workspace capabilities (search, read messages/threads, send messages, canvases, Lists) as tools for agents.
运行位置Where it runs: 官方托管远程 server（mcp.slack.com/mcp——直抓 401=存在需鉴权）； Streamable HTTP + JSON-RPC 2.0（官方文档口径）。旧 slackapi/slack-mcp-server 仓已 404（2026-10-21 直抓）。
Official hosted remote server (mcp.slack.com/mcp — direct fetch 401 = exists but needs auth); Streamable HTTP + JSON-RPC 2.0 (official docs wording). The old slackapi/slack-mcp-server repo is now 404 (direct fetch 2026-10-21).
本地文件Local files: 不碰本机文件系统——作用域是 Slack 云端工作区（消息、文件、canvases、Lists）。
Never touches the local file system — the scope is the Slack cloud workspace (messages, files, canvases, Lists).
关机后的任务Tasks after shutdown: 服务在 Slack 侧；会话请求-响应，无后台监听语义——「agent 不监视 Slack，等你问」。
The service lives on Slack's side; session request-response, no background-listening semantics — "the agent does not watch Slack, it waits for you to ask".
工具与扩展Tools & extensions: 搜索（消息/文件/用户/频道）、读频道与线程、发消息、建会话、reaction、 canvas 读写、用户档案、Lists 增删改查、文件上传（官方 changelog 2026-05 有新增工具记录）；完整清单以 docs.slack.dev 为准。
Search (messages/files/users/channels), read channels and threads, send messages, create conversations, reactions, canvas read/write, user profiles, Lists CRUD, file uploads (the official changelog has new-tool records for 2026-05); the complete inventory follows docs.slack.dev.
上下文与记忆Context & memory: 无 server 侧跨会话记忆——状态在 Slack 工作区本身；搜索工具是它的「取上下文」主手段。
No server-side cross-session memory — state lives in the Slack workspace itself; the search tools are its main means of "fetching context".
权限与限制Permissions & limits: 权限面是这条目的核心：OAuth user-token scopes 逐工具映射（search:read、chat:write、 canvases:write 等）+ 工作区管理员审批（admin 决定哪些 MCP 客户端可连）—— 未发布 Marketplace/内部 app 连不上。写动作（发消息/建会话）跟着授权 scope 走。
The permission surface is the core of this entry: OAuth user-token scopes mapped per tool (search:read, chat:write, canvases:write etc.) + workspace admin approval (admins decide which MCP clients may connect) — unpublished Marketplace/internal apps cannot connect. Write actions (sending messages/creating conversations) follow the granted scopes.
适合什么任务Best for: 适合：编码/研究 agent 取「团队在 Slack 里的决策与上下文」、总结频道、代拟消息。不适合：要事件触发自动化（MCP 不是触发器——要自动化走 Workflow/automation 线）；要 bot-token 无 OAuth 路线（官方走 user-token OAuth）。
Fits: coding/research agents fetching "the team's decisions and context in Slack", summarizing channels, drafting messages on your behalf. Not a fit: event-triggered automation (MCP is not a trigger — automation goes through the Workflow/automation line); bot-token routes without OAuth (the official line uses user-token OAuth).
传输方式Transport: Streamable HTTP（JSON-RPC 2.0），端点 mcp.slack.com/mcp。官方明写 SSE 与 Dynamic Client Registration 暂不支持（第三方核验页转述官方 docs）—— 客户端要走现行 remote MCP/OAuth 路径。核验：docs.slack.dev 200、端点 401（2026-10-21 直抓）。
Streamable HTTP (JSON-RPC 2.0), endpoint mcp.slack.com/mcp. The official docs state plainly that SSE and Dynamic Client Registration are not supported for now (third-party verification page paraphrasing the official docs) — clients must take the current remote MCP/OAuth path. Verified: docs.slack.dev 200, endpoint 401 (direct fetch 2026-10-21).
认证机制Authentication: OAuth 2.0 user-token 流（slack.com OAuth 端点授权）；工具逐一对应 scope。 管理员审批是前置门：工作区 admin 批准 MCP 客户端集成才能连。
OAuth 2.0 user-token flow (authorization at the slack.com OAuth endpoints); tools map one-to-one to scopes. Admin approval is a front gate: the workspace admin must approve the MCP client integration before it can connect.
权限范围Permission scope: 读面：搜索/历史/用户档案/canvas 读；写面：发消息、建会话、reaction、canvas 写、 Lists 写、文件上传。全部跟着 OAuth scope 与 admin 策略走；无工具级独立审批机制的官方说明。
Read surface: search/history/user profiles/canvas reads; write surface: send messages, create conversations, reactions, canvas writes, Lists writes, file uploads. All of it follows OAuth scopes and admin policy; no official docs for a tool-level separate approval mechanism.

头号误解Top misconception

把 MCP 当「agent 常驻 Slack」——它只在会话里响应，不监视不触发Treating MCP as 'an agent living in Slack' — it only responds within a session; it does not watch or trigger
用旧仓 slackapi/slack-mcp-server 找官方实现——已 404，现役是官方托管 mcp.slack.comLooking for the official implementation in the old slackapi/slack-mcp-server repo — it 404s; the live line is the hosted mcp.slack.com
把 reference 版（已归档、转 Zencoder 维护）当官方——本条目是 Slack 自营托管线Confusing the archived reference server (handed to Zencoder) with the official one — this profile is Slack's self-operated hosted line
忽略 admin 审批面——企业工作区连不上多半是 admin 策略，不是客户端 bugIgnoring the admin approval gate — in enterprise workspaces, failure to connect is usually admin policy, not a client bug

未知项清单Known unknowns

工具全清单与逐工具 scope 映射表（未逐条清点——docs.slack.dev 有页未逐条核）
admin 审批的粒度（按客户端/按 scope？未逐条核验）
速率限制细则（官方按 Web API 限流口径，数字未逐条核验）

The full tool inventory and the per-tool scope mapping table (not enumerated item by item — docs.slack.dev has pages not checked one by one)
The granularity of admin approval (per client/per scope? not verified item by item)
Rate-limit details (the official side follows Web API rate-limit wording, numbers not verified item by item)

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-30，内容更新日content updated on 2026-10-21。

类型Type	名称Name	链接Link
docs	Slack · 官方 MCP 文档（端点、传输、鉴权口径，2026-10-21 直抓核验）Slack · official MCP docs (endpoint, transport, auth wording, direct-fetched and verified 2026-10-21)	https://docs.slack.dev/ai/slack-mcp-server
changelog	Slack · 开发者 changelog（MCP 工具新增记录）Slack · developer changelog (MCP new-tool records)	https://docs.slack.dev/changelog
docs	Slack · 官方帮助中心 MCP 指南Slack · official help-center MCP guide	https://slack.com/help/articles/48855576908307-Guide-to-the-Slack-MCP-server

实测记录Measured runs

本档未在真实客户端逐项跑通；工具清单与权限来自官方 README。

This site has not completed measured runs. The test protocol is at protocols/mcp/_protocol.md.