Slack MCP Server
Slack MCP Server is an MCP server published by jtalk22, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does Slack MCP Server support the current MCP specification (2026-07-28)?
Not yet confirmed. Slack MCP Server is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is Slack MCP Server a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Slack MCP Server (as of 2026-08-20).
How do I connect to Slack MCP Server?
Slack MCP Server is available via a hosted remote endpoint at https://mcp.revasserlabs.com/oauth/mcp, the package npm:@jtalk22/slack-mcp, the official MCP Registry under io.github.jtalk22/slack-mcp-server, the source repository at https://github.com/jtalk22/slack-mcp-server. Authentication: oauth. Transports: streamable-http.
Does Slack MCP Server support MCP revision 2025-11-25?
Yes. Slack MCP Server supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Slack MCP Server support MCP revision 2026-07-28?
No. Slack MCP Server was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Slack MCP Server's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Slack for AI agents: DMs, search, threads, triage, actions - browser-session or hosted OAuth.
Which MCP spec revisions does Slack MCP Server support?
Slack MCP Server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is Slack MCP Server?
Ranked #354 in The MCP 500 with Adoption Index 48.17 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 262 | API · |
| GitHub stars | 30 | API · |
| GitHub forks | 22 | API · |
| Last push | 2026-09-11T10:48:06Z | API · |
| Repository archived | no | API · |
Repository and package signals for Slack MCP Server
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 2
- Primary language
- JavaScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- Present
Declared topics: agentic-ai, ai-agents, anthropic, claude, claude-code, claude-desktop, codex, copilot, cursor, developer-tools, gemini-cli, llm, local-first, mcp, mcp-server, model-context-protocol, productivity, slack, slack-api, slack-mcp — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
5.0.0- Last published
- First published
- Releases
- 47
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 3
- Unpacked size
- 315 KB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.jtalk22/slack-mcp-server at version 4.7.0 - lists remote endpoint https://mcp.revasserlabs.com/oauth/mcp and repository https://github.com/jtalk22/slack-mcp-server - accessed
- Endpoint probe of https://mcp.revasserlabs.com/oauth/mcp - authorization required (HTTP 401, Bearer realm="OAuth", resource_metadata="https://mcp.revasse); capability set not observable without credentials - accessed
- npm registry metadata for @jtalk22/slack-mcp at published version 4.9.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed