MCP (Model Context Protocol) server that exposes Slack workspace data via Stdio or Server-Sent-Events transports without requiring any Slack App installation or admin approval.
https://github.com/korotovsky/slack-mcp-serverTired of waiting weeks for admin approval to access your Slack workspace data? This MCP server gives you immediate access to conversations, channels, and threads without creating a single Slack App or bothering IT.
You want to feed your team's Slack discussions into Claude or other AI tools for analysis, summarization, or context. But the traditional path requires:
This MCP server sidesteps all of that by using your existing browser session or a simple user token.
Browser Token Method (2 minutes):
# Extract tokens from your browser's developer console
# XOXC token from localStorage
# XOXD token from cookies
npx -y slack-mcp-server@latest --transport stdio
User OAuth Method (5 minutes):
# Create a personal app at api.slack.com/apps
# Add basic read scopes, install to workspace
# Use the xoxp- token directly
Both methods give you full read access to channels, DMs, and threads you already have permission to see.
Meeting Follow-ups Made Automatic Ask Claude to pull the last 50 messages from #engineering-standup and generate action items. The server fetches full conversation history with context, including thread replies and user mentions.
Cross-Channel Context Discovery
"Show me all discussions about the new API from #backend-dev and #product-planning this week." The channels_list tool finds relevant channels, then conversations_history pulls the actual discussions.
Thread Analysis at Scale Point Claude at a long technical discussion thread and ask for a summary of the resolution. The conversations_replies tool pulls the entire thread structure, maintaining reply relationships.
Claude Desktop Setup (30 seconds):
{
"mcpServers": {
"slack": {
"command": "npx",
"args": ["-y", "slack-mcp-server@latest", "--transport", "stdio"],
"env": {
"SLACK_MCP_XOXP_TOKEN": "xoxp-your-token"
}
}
}
}
Docker for Remote Access:
docker run -e SLACK_MCP_XOXP_TOKEN=xoxp-... \
ghcr.io/korotovsky/slack-mcp-server \
mcp-server --transport sse
Pagination Handled Automatically: Request 200 messages, get proper cursor-based pagination without manual token management.
Channel Name Resolution: Use #general instead of cryptic channel IDs like C1234567890.
Activity Filtering: Toggle whether you want join/leave notifications included or just actual conversations.
Thread Context: Get complete thread hierarchies, not just individual messages.
The server supports both public channels and private DMs/group chats you're already part of. You can:
Perfect for AI-powered analysis of team communications, project retrospectives, or finding specific technical discussions buried in chat history.
Built in Go with minimal dependencies. Supports both Stdio (perfect for Claude Desktop) and SSE transports (great for web applications). The 2,000+ developers already using it in their workflows have stress-tested the reliability.
Docker support, proxy configuration, and TLS handling mean you can deploy it anywhere from local development to production environments.
The security model is straightforward: you're using your own Slack permissions. No escalated access, no bot management, no token rotation headaches.
Stop waiting for admin approval. Start analyzing your team's Slack data today.