Slack in Claude.
One URL. No setup.

Add one block to your MCP config. Get full Slack access in Claude Desktop, Claude Code, or any MCP client. No OAuth, no admin approval, no Docker.

Get Your API Key Self-Host Free
claude_desktop_config.json 
// That's it. The whole config.
{
  "mcpServers": {
    "slack": {
      "url": "https://mcp.revasserlabs.com/mcp",
      "headers": {
        "Authorization": "Bearer stmh_your_key"
      }
    }
  }
}
Working in under 60 seconds. Not 45 minutes.

Who this is for

Solo developers who use Claude with Slack and don't want to maintain infrastructure. Engineers whose IT team won't approve the official Slack MCP app. Freelancers working across multiple client workspaces. Anyone who has screenshotted a Slack message to paste into Claude.

Why not just self-host?

You can. It's free, MIT-licensed, and it works. But there are trade-offs.

Self-hosted

Tokens expire silently

Session tokens are time-bounded. When they expire, your Claude workflow breaks mid-conversation. You re-extract from Chrome and try again.

Cloud

Tokens refresh automatically

Encrypted token storage with auto-refresh. Your endpoint stays live. You never touch Chrome DevTools again.

Official Slack MCP

Requires OAuth and admin approval

Slack's official MCP needs a Marketplace-approved app. Your IT team has to approve it. Enterprise-only.

Cloud

Works where OAuth can't

Session-based auth. No Marketplace listing, no admin approval, no IT ticket. Individual developers can start immediately.

16 Slack tools, ready to use

Everything you need for full Slack access from Claude. Every plan, including self-hosted.

→
slack_list_conversations
List channels and DMs
→
slack_conversations_history
Read channel messages
→
slack_search_messages
Search across workspace
→
slack_send_message
Send messages
→
slack_get_thread
Read thread replies
→
slack_get_full_conversation
Export full history
→
slack_users_info
Get user details
→
slack_list_users
List workspace members
→
slack_health_check
Verify connection
→
slack_token_status
Check token health
→
slack_refresh_tokens
Auto-refresh credentials
→
slack_add_reaction
React to messages
→
slack_remove_reaction
Remove reactions
→
slack_conversations_mark
Mark as read
→
slack_conversations_unreads
Unread inbox
→
slack_users_search
Search users

Team plan: compound intelligence

Three additional tools that process your Slack data server-side. Available on the Team plan.

slack_channel_summary Team
> Summarize #product this week Key Topics - Q2 roadmap finalized: mobile + API v3 - Design system migration approved Action Items @sarah: Update pricing page by Friday @mike: Review API docs PR #247 50 messages processed
Structured summary of any channel. Topics, decisions, action items.
slack_extract_action_items Team
> Action items from #engineering Open Items 1. @chen: Deploy Redis cache by EOD 2. @priya: Write migration script 3. @team: Review RFC by Wednesday Blocked - Load test results (waiting on #2) 35 messages processed
Extract action items with owners, deadlines, and blockers from conversations.
slack_find_decisions Team
> Decisions in #ops this month Confirmed 1. Migrate from AWS to Cloudflare @cto · Mar 8 2. Freeze feature work until Q2 @pm-lead · Mar 7 40 messages processed
Surface decisions and commitments buried in conversations.

Pricing

Self-hosted is free forever. Cloud adds managed hosting and convenience.

Self-Hosted
Free
Full server on your machine. You manage tokens.
  • 16 MCP tools
  • stdio + SSE transport
  • Chrome token extraction
  • MIT licensed
Install Free
Solo
$19 /mo
Hosted endpoint with managed tokens. Zero maintenance.
  • 16 MCP tools
  • Auto token refresh
  • Encrypted storage (AES-256)
  • 1 workspace
  • 5,000 requests/mo
Start Solo — $19/mo
Team
$49 /mo
Everything in Solo, plus compound intelligence tools.
  • Everything in Solo
  • 3 AI compound tools
  • 3 workspaces
  • 25,000 requests/mo
  • Priority support
Start Team — $49/mo

Launch pricing — locks in for as long as you're subscribed.

Need dedicated infrastructure, SLA, or compliance? Contact us.

How it works

1

Choose a plan

Complete checkout in 30 seconds via Stripe.

2

Get your API key

Receive your endpoint URL and bearer token instantly.

3

Paste one config block

Add to Claude Desktop, Claude Code, or any MCP client.

4

Ask Claude about Slack

"What happened in #engineering today?"

Security

Encrypted at rest

Tokens encrypted with AES-256-GCM on Cloudflare's edge network. Your credentials never touch a traditional server disk.

Messages never stored

Slack messages pass through for processing. They are never stored, logged, or used for training. AI tools analyze in-flight only.

Cloudflare Workers

Runs on SOC 2 Type II infrastructure with 300+ global PoPs. No server, no disk, no persistent memory.

Fully auditable

All source code is MIT-licensed and open on GitHub. Read every line before you buy.

v3.2
current release
25+
releases shipped
AES-256
token encryption
300+
Cloudflare edge PoPs

Open source core. MIT licensed. Powered by Cloudflare Workers. Source on GitHub.

Questions

How is this different from Slack's official MCP?
Slack's official MCP requires OAuth, a Marketplace-approved app, and admin approval. This server uses session-based auth. No approval needed. Works for individual devs in any workspace.
What are session tokens?
Session tokens (xoxc + xoxd) are the same credentials your browser uses when you're logged into Slack. They work without creating an OAuth app or getting admin approval.
Is my Slack data stored on your servers?
Tokens are encrypted at rest with AES-256-GCM. Slack messages pass through for processing but are not stored. The AI compound tools (Team plan) analyze messages in-flight and return results without persistence.
Can I try before I pay?
The self-hosted server is free and includes all 16 standard tools. Cloud adds managed hosting, auto-refresh, and (on Team) AI compound tools.
Which MCP clients are supported?
Claude Desktop, Claude Code, and any client that supports the MCP protocol over HTTP/SSE. The self-hosted version also supports stdio transport.
How is this different from other open-source Slack MCP servers?
Most open-source Slack MCP servers require you to self-host, manage your own tokens, and restart when tokens expire. This Cloud service eliminates all of that: one API key, auto-refreshing tokens, encrypted storage, and three AI compound tools that no self-hosted server offers.
What happens if I exceed my request limit?
Requests are rate-limited per plan (5,000/mo Solo, 25,000/mo Team). If you approach your limit, upgrade your plan or contact us for a custom quota. Overage requests return a clear rate-limit response — nothing breaks silently.

One config block. Full Slack access.

Start with the free self-hosted server or get a managed Cloud endpoint in 60 seconds.

Get Your API Key Read the Docs