Slack MCP Server
Give your AI agent full Slack access — and structured workflow output the AI can actually use. No app registration, no admin approval, no OAuth. One command, 21 tools, works with any MCP client.
npx -y @jtalk22/slack-mcp --setup▶ Watch the demo — 7 scenarios, from 47 unreads to inbox zero, without opening Slack.
Ask your AI to catch you up on #engineering from the last 24 hours. Search for that deployment thread from last week. Find the printer admin PIN nobody can remember. Send a reply. All from your editor.
Interactive demo · Latest release
Why This Exists
Slack's official MCP server is OAuth-first and can require a registered app, admin approval, or client compatibility workarounds. See the tracked Claude Code/GitHub Copilot compatibility discussion. Screenshotting messages is not a workflow.
This server uses your browser's session tokens instead. If you can see it in Slack, your AI agent can see it too. No app install, no scopes, no admin.
Session-token transport: No bot user appears in the workspace admin panel, no app install shows up, no audit trail entry is created. Your AI agent operates with the same workspace footprint as your browser tab — nothing more, nothing less.







