korotovsky/slack-mcp-server — The most powerful MCP Slack Server with no permission requirements, Apps support, GovSlack, DMs, Gro…

Description and use

**Brief Summary (2‑3 sentences)**
korotovsky/slack-mcp-server is an open‑source Go implementation of the Model Context Protocol (MCP) for Slack, offering a fully‑featured Slack‑compatible server with zero permission requirements, support for Slack Apps, GovSlack, direct and group DMs, and an intelligent history‑fetching engine. It enables AI assistants to interact with real Slack workspaces and tools using a standard, low‑friction API, making it a strong candidate for production‑grade pilots.

**Value**

• **Standardised bridge** – By exposing a clean MCP‑based API, the server lets any MCP‑compatible AI model (e.g., Claude, GPT‑4o) read from and write to Slack channels, DMs, and GovSlack environments without dealing with Slack’s OAuth flow or rate‑limit quirks.
• **Feature‑rich out‑of‑the‑box** – Built‑in support for Apps, group DMs, and a “smart history” fetch layer reduces the engineering effort required to give agents context‑aware conversation histories.
• **Open‑source & community‑backed** – 1.6 k stars, 300+ forks, and active commits (last update 2026‑05‑14) signal a healthy ecosystem and rapid bug‑fix turnaround.

**Practical Adoption Path**

| Step | Action | Why it matters |
|------|--------|----------------|
| 1️⃣ | **Clone & build** – go build ./... (requires Go 1.22+). | The project is a single Go binary, so deployment is straightforward on any container host or VM. |
| 2️⃣ | **Configure** – Provide a minimal config.yaml with your workspace ID, optional bot token (if you need privileged actions), and MCP endpoint settings. | No OAuth scopes are required for basic read/write; you can start with a read‑only sandbox and later add a token for richer interactions. |
| 3️⃣ | **Run** – ./slack-mcp-server -c config.yaml. | The server starts listening on the MCP HTTP/WS ports, exposing /api/v1/events, /api/v1/message, etc. |
| 4️⃣ | **Connect your AI agent** – Point the agent’s MCP client library (available for Python, Node, Go) at the server’s URL. | The agent now can fetch channel history, post messages, and react to events using the same protocol it would with a real Slack API. |
| 5️⃣ | **Iterate & secure** – Add TLS, enable optional JWT auth, and optionally supply a Slack App token for privileged actions. | Moves the setup from a sandbox to a production‑grade deployment while keeping the zero‑permission baseline for most use‑cases. |
| 6️⃣ | **Monitor & scale** – Use the built‑in /metrics endpoint (Prometheus format) and horizontal scaling via Docker/K8s. | Guarantees observability and the ability to handle higher message volumes as the AI‑assistant usage grows. |

**Production Readiness**

• **Activity & maintenance** – Recent commits (as of 2026‑05‑14), a healthy star/fork ratio, and multiple contributors indicate active stewardship.
• **Maturity** – The server already implements core Slack features (DMs, group DMs, GovSlack) and includes a sophisticated history‑caching layer, reducing latency and API‑call costs.
• **Deployability** – Single‑binary Go service, container‑friendly, with Prometheus metrics and optional TLS/JWT hooks, fits typical production CI/CD pipelines.
• **Risk considerations** – License (MIT) is permissive, but a final security audit is advisable, especially if you plan to expose a Slack token for privileged actions.

Overall, korotovsky/slack-mcp-server is production‑ready for pilots that need a reliable, standards‑based bridge between AI agents and Slack‑like communication channels, with a clear upgrade path to hardened, enterprise deployments.

Problem

korotovsky/slack-mcp-server helps connect AI assistants to real tools and data through a standard protocol.

Outcome

High for an OSS candidate: recent activity, adoption, and ecosystem signals are strong enough for a serious pilot.

Workflow

• connect AI agents to tools
• ship Model Context Protocol servers
• standardize integrations

Evidence

The most powerful MCP Slack Server with no permission requirements, Apps support, GovSlack, DMs, Group DMs and smart history fetch logic.

Source