Slack MCP Server

    

Slack MCP Server

Catch up on Slack without reading it.

Unreads, threads, and search — in your agent’s context, from the session you already have.

npx -y @jtalk22/slack-mcp --setup

Claude Code Claude Desktop Cursor Copilot Windsurf Gemini CLI Codex CLI any stdio MCP client

▶ It’s Monday, 9:07—watch what blew up overnight · interactive walkthrough · setup guide

How it works · Why session auth · Grid & credentials · Install · 19 tools · Workflows · Local vs hosted

It’s Monday, 9:07. Slack has already formed opinions.

You ask “what blew up overnight?” and the agent reads the workspace instead of you. It reconstructs the 2 AM P1 from #incidents—owner, resolution, and the runbook step that is still wrong. It finds the printer PIN that has been waiting in #facilities for five months. Then it closes the handled loops—replies, reactions, read-state changes—only where you approve.

This is not screenshot automation. The agent calls Slack through a real MCP tool surface and receives typed results it can search, summarize, export, or act on.

Built past the demo

The difficult part is not another chat tool. It is the operating layer underneath: browser-session extraction that names its failure stages, a credential lifecycle built for rotation, full-fidelity reads, guarded writes, and typed workflow output. The code is plain JavaScript in this repository—audit it before trusting it with a session.

The engineering underneath — extraction, credential lifecycle, reads, guarded writes, typed output

1. The browser-session engine

--setup turns the Slack identity Chrome already holds into a local MCP server:

Shortened. The full README is on GitHub.