MCP guides · Slack
Slack MCP is the quiet workhorse of an agent team setup.
Most decisions, commitments, and follow-throughs live in Slack threads, not CRM fields. An agent that can read them ends the 'did we follow up' guessing game.
The problem
Why this matters
Slack ate the work. Every promise, every status update, every 'I'll handle it', every escalation, all of it lives in a thread. The CRM record is downstream. The doc is downstream. The decision happened in Slack.
Which means any AI tool that does not read Slack is reasoning from a partial picture. The summary it generates looks fine and is wrong, because the actual commitment was made in #cs-eng-sync on a Tuesday.
MCP plus Slack closes that gap. An agent that can search and read your channels and DMs (with the boundaries you set) answers 'did we follow up,' 'who owns this,' 'what did we agree to' from real evidence, not from memory.
What you get
What MCP unlocks here
Search across channels you actually live in
An agent that can run Slack search ('from:customer in:cx-team after:7d') and read threads becomes the institutional memory you have always wished for. No more 'I think we discussed this somewhere'.
DM as you, only when you tap approve
MCP lets the agent draft a DM in your voice based on the thread context. The safe posture is draft, you approve, send. The 'AI replied to my CFO without my okay' fear is structurally avoidable.
Cross-tool reasoning that finally works
Slack thread plus CRM record plus calendar event becomes one conversation the agent can reason about. 'The customer flagged churn in #cx-team, the deal is at risk in Salesforce, the renewal call is in two weeks.' One picture, one next action.
Channel notifications that don't drown you
Have the agent watch specific channels and surface only what matters (a named customer mention, a teammate's escalation, a CEO ask). Slack's native notifications are blunt; an agent filter is precise.
Setup
Three steps to a working agent
Install a Slack MCP server
Community-maintained Slack MCP servers wrap conversations.history, conversations.replies, search.messages, chat.postMessage, and users.lookupByEmail. For founder-stage use, install at user-token scope so the agent acts as you in your channels.
Decide which channels the agent reads
Default: only the channels you are already in. Be explicit about excluding sensitive ones (compensation, legal). Most teams scope DMs to read-only and channel writes to draft-only. The agent does not need access to everything to be useful.
Give the agent a job that touches Slack
'Every morning, tell me which customer threads in #cs-team need a reply.' 'When a teammate asks me a Slack question, draft an answer for me to approve.' 'Surface every promise I made in Slack last week that I have not closed.' The job is where Slack MCP earns its keep.
Signal
What people doing this say
We stopped tagging '@here did anyone do this' in #cs-team. The agent just answers from the threads.
Head of CX, B2B SaaS (paraphrased)
Slack MCP plus a CRM connector is how I finally have a single source of truth across the conversation and the deal.
Founder, fintech
Most AI sales tools reason from CRM only. The real work is in Slack threads. MCP lets the agent see both.
Patrick Hillstrom, Nerve
FAQ
Common questions
Will the agent see my private DMs?
Only at the scope you grant. User-token MCP servers see what you see. Bot-token servers see only channels they are invited to. For founders running their own agent, user-token in your own workspace is the usual choice. Make sure your teammates understand the posture.
Can the agent reply in a channel as me without my approval?
Only if you scope it to. The default is draft, approve, send. Most teams keep this posture for at least the first 30 days. Auto-reply (where the agent posts directly) is reserved for very narrow workflows you trust.
How does this interact with Slack's own AI features?
Slack's native AI (channel summaries, recap) is intra-Slack only. An MCP-connected agent reasons across Slack plus your CRM plus your inbox plus your calendar. Different unit: summary inside Slack vs. agent across your stack.
What about Slack Enterprise Grid and DLP?
Grid admins control which apps can install. The MCP server should be reviewed and approved like any third-party Slack app. Some enterprises require Slack-approved app directory listings; for those orgs, expect a longer install timeline.
Does Nerve use Slack MCP?
Yes, both as a connector (reading Slack into Nerve) and exposed through the Nerve MCP server (so external hosts can act on our state). Patrick's day starts with a Nerve briefing that includes the relevant Slack threads alongside the email and pipeline state.
Who this is for
Roles where this matters most
Nerve for account executives
Account executives carry a number and run a pipeline. Nerve is the AI agent team that handles the pre-call prep, post-call followup, and pipeline hygiene so your selling time stays on the calls that close.
Nerve for customer success managers
CSMs carry a book of accounts and own retention. Nerve is the AI agent team that surfaces at-risk accounts, drafts QBR materials, and keeps every customer warm without dropping the depth on the few that matter most.
Nerve for engineering managers
Engineering managers spend half their time on the meta-work: status updates, cross-team coordination, 1:1 prep, performance signal. Nerve is the agent team that does the meta-work so you can ship the actual work.
Nerve for product managers
Product management is mostly coordination. Nerve is the AI agent team that runs the stakeholder updates, customer interview notes, and cross-team handoffs so your time stays on the work that requires you.
Nerve for operations leaders
Operations leaders absorb whatever the org can't put into a function. Nerve is the AI agent team for the structural work so your judgment ends up on the high-leverage calls, not the weekly slack.
Nerve for recruiters
Recruiting is a sales pipeline with worse forecasting and weirder buyers. Nerve runs the operations layer so your selling time stays on the calls that move searches forward.
End the 'did we follow up' guessing game.
Start free, no credit cardMore MCP guides
Other MCP guides
The best MCP servers for founders, ranked by real founder workflows
MCP turns Claude into an agent team that touches your actual stack. These are the MCP servers a working founder hooks up first, why each one matters, and how Nerve wires them together.
Best MCP servers for sales teams: the pipeline-grade stack
The MCP servers a working sales team actually uses, ranked. CRM, inbox, calendar, and conversation surfaces, with notes on what each one does well and where it falls short.
MCP server setup guide: from zero to a working agent in 30 minutes
The honest guide to installing your first MCP server with Claude. Hosts, auth, gotchas, and what to do after the hello-world example works.
Claude MCP integration for Gmail: a working founder's setup guide
How to wire Gmail to Claude over MCP so an agent can triage, search, and draft from your real inbox. The 15-minute setup, the gotchas, and what changes when it's live.
Claude MCP integration for Google Calendar: real meetings, no swivel-chair
How to wire Google Calendar to Claude over MCP so an agent can find time, book meetings, and reason about your week without screenshots or back-and-forth.
Claude MCP integration for Salesforce: an agent that writes the right field
How to wire Salesforce to Claude over MCP so an agent can read your pipeline, log activities, and update deals without you swivel-chairing between tabs.