"Slack" matching MCP servers:

MCP Server for the Slack API, enabling Claude to interact with Slack workspaces.

Interact with Slack Workspaces over the Slack API. Supports stdio and Streamable HTTP transport. Extended from Anthropic's archived server

MCP server that reads Slack through your own browser session, authenticating as you rather than a bot. Provides tools to search messages, retrieve channel/DM/thread history, resolve users, and post messages (write disabled by default).

An MCP server for semantic search and retrieval of indexed Slack messages stored in Qdrant using Cohere reranking via AWS Bedrock. It enables users to search through Slack history, retrieve full message threads, and access channel or user statistics through natural language.

Enables reading, searching, and downloading files across multiple Slack workspaces via per-workspace user tokens, plus drafting and confirmed sending of messages and attachments.

Enables Slack integration with tools to list channels, read messages, and post messages using a bot token.

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

Enables Slack workspace integration including channel creation, user invites, message posting, and thread management through natural language.

Enables AI assistants to interact with Slack workspaces, providing tools for reading messages, posting content, managing channels, and more.

MCP server for Slack workspace integration, exposing 40+ Slack operations as tools for Claude Desktop and providing a clean async Python API.

Enables an AI assistant to act as the user in Slack through a user OAuth token, covering messaging and threads, search, users, channels, user groups and reactions, plus scheduled messages, canvases and Slack Lists. It also supports flexible channel addressing by ID, #name or @user, and matches existing tool names and parameters for seamless integration with established prompts and permission rules.

Provides LLMs full access to Slack: messages, channels, files, canvases, lists, search, reactions, and more via 220 tools and 36 API families.

Enables reading Slack channels, messages, and threads using the web interface via a persistent browser session, designed for guest users without API access. Does not send messages.

A self-hosted, read-only Slack MCP server that runs locally and provides read-only access to Slack channels, messages, and users via the Slack Web API, with no third-party intermediary.

Lets you @mention a bot in a Slack channel or DM to send work to a local Claude Code session and watch it run, with live self-updating turn cards, threaded answers, progress checklists and a per-channel inbox with read cursors. It runs entirely on your machine over Slack Socket Mode—no tunnel or public IP—routes misdelivered messages to the right project, and masks credentials in anything it posts back.

Enables bidirectional communication between MCP clients and Slack, allowing users to receive task notifications and respond to AI inquiries directly within Slack threads. It supports various urgency levels, message threading, and interactive question-and-answer workflows.

An MCP server that enables AI agents to send messages, payloads, and Markdown-formatted content to Slack via Incoming Webhooks.

Local MCP stdio bridge to Slack's hosted MCP server, enabling agents to use Slack tools (send messages, search, history, canvas, etc.) via local OAuth and token refresh.

Enables triggering Jenkins builds from IDEs with Slack notifications, requiring only a one-time login.

Enables AI agents to operate in Slack as a bot, sending direct and channel messages, finding members, reading history and threads, adding reactions, and waiting for or checking replies.