Your team’s real knowledge doesn’t live in documents — it lives in Slack threads. Decisions, context, that one message where someone explained the whole problem. The trouble is getting it out: scrolling, searching, copy-pasting conversations into an AI chat one screenshot at a time.
The Slack MCP connector ends that. Once connected, Claude can search your workspace, read channels and threads, summarize what you missed, and even post messages on your behalf — all from inside a Claude conversation. We set it up, tested it, and ran into the exact blockers you’re likely to hit, so this guide covers those too.
What Claude Can Do Inside Your Slack
- Search everything you have access to. Messages, files, people, channels — “find the thread where we decided on the pricing change” works even if you don’t remember which channel it was in.
- Read and summarize channels or threads. “What did I miss in #general this week?” becomes a 30-second catch-up instead of a 20-minute scroll.
- Send messages and reply in threads. Claude can draft and post — and anything it posts appears as coming from you, so treat that power accordingly.
- Work with Slack canvases. Create and read canvas documents directly from the conversation.
- Show a live Slack view. Since the January 2026 update, Slack runs as an interactive app inside Claude — you see an actual Slack interface in the chat, not just text output.
One boundary to understand before you connect: this is an assistant you operate, not an agent that watches. Nothing triggers automatically — Claude only touches Slack inside a conversation you start. No “alert me when someone mentions the project” and no background monitoring. For a solo operator or a small team, that’s usually exactly the right amount of power.
What You’ll Need
- A Claude account (claude.ai or Claude Desktop)
- A Slack workspace — the free Slack plan works
- Permission to install apps in that workspace (more on this in the gotchas — it’s the #1 blocker)
- About five minutes
Step-by-Step Setup (2026)
Step 1: Open Connectors in Claude Settings
In claude.ai, click your profile icon in the bottom-left corner, then go to Settings → Connectors. Slack is in the connectors directory alongside Gmail, Google Drive, and the rest.
Step 2: Connect Slack
Click Connect next to Slack. You’ll be sent to Slack’s sign-in page — choose the workspace you want Claude to access and log in.
Step 3: Approve the permissions
Slack shows a consent screen listing what Claude will be able to do. Review it and approve. Same habit we recommend for every connector in this series: make sure nothing on the consent screen is left unticked — a partial grant produces a connection that looks fine but fails silently later.
Step 4: Enable the connector in your chat
Open a new Claude chat and click the + button near the message box. Toggle Slack on for this conversation. Connectors are per-chat, so if Claude claims it can’t see Slack, this toggle is the first thing to check.
Step 5: Run a test prompt
“List the channels I’m a member of, and summarize the last five messages in the most active one.”
Real channel names and real messages back means you’re connected.
5 Real Prompts to Try First
- The Monday catch-up: “Summarize what happened in #general and #projects since Friday. Group by topic and flag anything that needs a reply from me.”
- The decision finder: “Search Slack for the discussion about [topic] and tell me what was decided and by whom.”
- The thread-to-brief: “Read this thread in #client-work and turn it into a short status update I can send to the client.”
- The drafted reply: “Draft a reply to the latest message in #support explaining [answer] — show me before posting.”
- The meeting prep combo: If you’ve also connected Google Calendar and Gmail — “Look at my next meeting, find related Slack discussions and emails, and brief me in one paragraph.”
Prompt #4 shows the habit worth building from day one: since Claude posts as you, always ask to see the draft before it sends. One extra sentence in the prompt, zero surprises in the channel.
Five Gotchas We Hit (So You Don’t Have To)
1. The admin approval wall
This is the single most common blocker. Many workspaces restrict which apps members can install — if the OAuth flow refuses to complete, the fix isn’t retrying. Your workspace admin needs to approve the Claude app in Slack’s app management settings. If you’re the admin of your own small workspace, you’ll sail through; in a client’s or employer’s workspace, send the request first.
2. Claude only sees the channels you’ve joined
Search covers channels the connected user is a member of. Private channels you’re not in are completely invisible — and so are public channels you never joined. If a search comes back oddly empty, join the relevant channel first, then ask again.
3. Free Slack plan = capped history
On Slack’s free tier, message history is limited, and Claude cannot read past that window — older threads simply return nothing. This is a Slack plan limitation, not a connector bug, so no amount of reconnecting will fix it.
4. Big sweeps hit rate limits
“Summarize everything in all channels from the last month” will run slow or come back partial — broad reads bump into Slack’s API rate limits. Scope your prompts by channel and time window (“#general, last 7 days”) and break big catch-up jobs into smaller asks.
5. It posts as you
Worth repeating as its own gotcha: messages Claude sends appear as coming from your account, with no “sent by AI” label. Our rule during the first week: read-only prompts freely, posting only after reviewing the draft, and only in channels where a mistake is cheap.
Troubleshooting
- OAuth won’t complete. Gotcha #1 — ask your workspace admin to approve the Claude app.
- Claude says it can’t access Slack mid-conversation. Check the + menu toggle for this specific chat.
- Searches return nothing for a topic you know exists. Either you’re not in that channel (gotcha #2) or the messages are older than your Slack plan retains (gotcha #3).
- Responses are slow or incomplete on big requests. Rate limits — narrow the channel and time window.
FAQ
Does the Slack connector cost anything?
Slack provides its MCP server at no extra charge, and it works with free Slack workspaces (within the history limits above). On the Claude side, the connector is part of the standard connectors directory — check your plan’s current connector availability.
Can my teammates see what Claude reads?
No — Claude’s reads and searches aren’t broadcast to the channel. Only messages you have Claude post are visible, and they appear as normal messages from you.
Can Claude monitor a channel and alert me?
No. The connector works only inside conversations you start — there are no triggers, schedules, or background monitoring. If you need event-driven automation, that’s a different tool category (a workflow platform like Zapier, which also connects to Claude via MCP).
Is it safe for a client’s workspace?
Claude inherits exactly your permissions — it can’t see anything you can’t. That said, in a client workspace the admin approval step (gotcha #1) means the client will know an AI app is connected. Be transparent about it; it’s also simply the professional move.
The Bottom Line
If your work lives in Slack, this is one of the highest-leverage connectors in the directory. The Monday catch-up prompt alone — one paragraph instead of an hour of scrolling — pays back the five-minute setup in the first week. Start read-only, keep the posting on a short leash, and let the search do the heavy lifting.
For every Claude connector we’ve tested and verified, check the full MCP Directory.
You Might Also Like
More tested guides from our MCP series:
Related Posts
