Skip to content
Menu

MCP server / communication / source-linked

Slack MCP

Slack MCP brings conversation evidence into an agent: messages, threads, files and people. Its practical value is recovering why a team made a decision, then preparing a follow-up. First distinguish the current Slack service from the archived reference package linked by older tutorials.

Before you choose.

Identify the implementation and the job it supports.

Which implementation is this?
Use Slack's vendor-hosted MCP service for a new setup. The original modelcontextprotocol Slack reference is archived; it is a different implementation.
Implementation source ↗

Slack MCP brings conversation evidence into an agent: messages, threads, files and people. Its practical value is recovering why a team made a decision, then preparing a follow-up. First distinguish the current Slack service from the archived reference package linked by older tutorials.

Setup and connection.

The documented interface, authentication and installation path.

Connection / transport
Streamable HTTP; no SSE
Authentication
Confidential OAuth using a registered Slack application's client ID and secret

Use https://mcp.slack.com/mcp through a supported client or registered internal app. Complete user authorization with only the scopes needed. Slack does not offer dynamic client registration; an arbitrary URL-only client may not complete setup.

Setup reference ↗

What it actually exposes.

Concrete capabilities with maintainer sources.

Documented capability / 01

Search workplace evidence

Search messages and files, then read the matching channel or complete thread for context.

Documentation ↗
Documented capability / 02

Prepare and publish messages

The service includes draft, send and schedule operations; sending requires chat:write.

Documentation ↗
Documented capability / 03

Work with canvases

Read canvases as Markdown and create or update shared canvas content.

Documentation ↗

Evidence and method.

What was checked and what was not tested.

WHO

Editorial record

Compiled by clawbot.ai.

HOW

Source method

Public maintainer documentation and repositories. This is not a hands-on product review.

WHEN

Last checked 2026-10-01

Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.

Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.

Community signals.

Concrete reports from public community discussions, kept separate from product documentation.

GitHub issue (Claude Code) / permissions / negative / issue2026-07-09 · mariusehrhart

Slack remote MCP unauthenticatable after Claude Code 2.1.195

用户在 macOS、Claude Code 2.1.197 中复现 Slack 官方远程 MCP 认证失败。升级 2.1.195 后原有凭据失效,新的 OAuth 因 Slack 未提供 DCR 或 CIMD 元数据而报 incompatible auth server;无自建 Slack app 权限的组织没有可行替代路径,headless 自动化也被阻断。

“Fresh zero-config OAuth against mcp.slack.com cannot succeed without a user-supplied client id.”
Open community source ↗
GitHub issue / reliability / negative / issue2026-03-09 · PatrickV-code

Startup rate-limited on large Enterprise Grid workspaces after v1.2.3

在约 6,700 用户、2,500 个频道的 Enterprise Grid 上,v1.2.3 冷启动会连续分页抓取用户与频道,触发 Slack rate limit,缓存只写入约 145 个频道,stdio 客户端随后超时重试并再次触发限流。报告给出 SLACK_MCP_CACHE_TTL=24h 和预热缓存作为临时缓解。

“channel cache was incomplete or startup failed entirely on an Enterprise Grid workspace.”
Open community source ↗
Reddit r/mcp / coverage / mixed / firsthand2026-06 (shown as 4 months ago) · No_Iron1885

Slack's MCP Can't Set a Channel Topic. I Benchmarked How Bad It Gets.

作者公开了 48 个相同 Slack 工作区任务的对照测试,覆盖读取、搜索、写入、频道管理和多步流程。官方 MCP 成功率 23%,对照服务器 77%;主要差距来自缺失 setTopic、reactions、unarchive、invite 等工具,而不是模型不会规划。作者同时披露自己维护对照服务器。

“Slack 23% success / Hintas 77% success across 48 prompts.”
Open community source ↗

Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.

Try a specific task.

A bounded evaluation you can reproduce in your own environment.

Proposed workflow: reconstruct a release decision

Suggested evaluation, not an observed test result.

  1. Name the release, channel and time window in the request.
  2. Retrieve the matching discussion and separate decisions from unresolved questions.
  3. Draft a summary with message links; ask for review before publishing it.

What to inspect: A decision brief that readers can verify against the original conversation. Not a tested accuracy benchmark.

Workflow reference ↗

Permissions and limitations.

Read these constraints before granting access.

Boundary / 01

Only Slack Marketplace apps and internal apps may use the official service; unlisted applications are excluded.

Boundary reference ↗
Boundary / 02

Editorial inference: reading a matching message alone can miss later corrections. Retrieve the thread before treating a search hit as a decision.

Boundary reference ↗

Decide by workflow.

Make the expected output explicit before you connect.

A decision brief that readers can verify against the original conversation. Not a tested accuracy benchmark.

Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.

Compare the alternatives.

Specific reasons to choose another route, with the tradeoff shown.

Editorial decision guidance inferred from the linked documentation; no quality or speed benchmark.
AlternativeChoose it whenTradeoff
Notion MCPEditorial choice: the authoritative material is maintained as pages and databases.Does not replace the conversation trail used to reach a decision.
Documentation ↗
Linear MCPEditorial choice: convert confirmed decisions into tracked engineering work.Issue tracking is a different source of truth from chat history.
Documentation ↗

Questions before setup.

Answers specific to this implementation.

Should I install the old reference Slack package?

Treat that package as historical. The MCP repository marks it archived; use the current vendor service for this guide.
Documentation ↗

Can every MCP client authenticate automatically?

No. Client registration and confidential OAuth support are required; dynamic client registration is not supported.
Documentation ↗