GTM MCP servers: the directory for sales and marketing teams
Every official MCP server and Claude connector a go-to-market team can wire in today, grouped by job, with what it reads, what it writes, and the one command that adds it.
By Vikash Koushik, Head of AI GTM Systems at Docket · Verified Sep 5, 2026
A GTM team's data lives in a dozen systems: the CRM, the enrichment tool, the call recorder, the sequencer, Slack, the wiki, the billing system. For most of the last two years the way to get any of it in front of an AI was to export a CSV and paste it in, and the way to get an answer back out was to copy it by hand. That courier work is where most AI-for-sales pilots quietly died.
MCP, the Model Context Protocol, is the open standard that removes the courier. A vendor runs a server that exposes its data and actions as tools; Claude connects to it once, with your login, and can then read a deal, pull a transcript, or draft a sequence step from inside a conversation or a scheduled run. Anthropic's apps call these connectors; Claude Code calls them MCP servers; they are the same thing. The plain-language explainer covers the protocol; this page is the directory.
Every row below is an official, vendor-run server or a connector Anthropic ships, verified against the vendor's own documentation on the date at the top of this page. Community wrappers are left out on purpose: they break, they lag the API, and they are the wrong thing to hand a rep's login to. Where a tool has a full integration guide on this site, the row links to it.
What an MCP server gives a GTM team
The first gain is the obvious one: Claude answers questions from live data. Which deals went quiet this week, what the last call with an account covered, who at the prospect has been enriched and who is still a bare email. No report to build, no export to drag in, and the answer reflects what the CRM says right now, which matters in a Monday pipeline review.
The second gain is the one that changes the economics: actions. A server that exposes write tools lets Claude log the call note, create the task, enroll the prospect, or post the digest, and that is what turns a chat into a workflow. It is also where the risk lives, so every row below states its read and write posture plainly, and the site's recurring advice holds: let Claude read freely and gate every write behind your approval until the pattern has earned trust.
The third gain is that the same connection serves both surfaces. Wire HubSpot once and it works in the Claude app for on-demand questions and in Claude Code for the plays that run on a schedule, like the Monday pipeline digest or the nightly lead scoring run. One login, two modes of work.
Adding a server takes one command, or one click
In the Claude apps, open Settings, then Connectors, find the tool in the directory, and sign in with your own account in the browser. The connection inherits your permissions in that tool, so Claude can never see or change more than you could yourself. Connectors need a paid Claude plan; the connectors guide walks the app side in detail.
In Claude Code, add the server's URL with the transport flag, then run the slash command to authorize it in the browser. Scope it to the user if you want it in every project, or to the project if the team should share it through version control. The commands below are the real ones; swap the URL for the server you want from the directory.
Read before writeTreat the directory as two lists. Read tools (transcripts, deals, contacts, pages) are safe to allow on day one; a wrong read costs you nothing. Write tools (create a task, enroll a prospect, refund a charge, update a deal) change the system everyone else reports from, so keep them behind an approval until you have watched the pattern run clean for a few weeks. The servers that can move money or email a customer, Stripe and Gmail among them, deserve the strictest gate.
GTM MCP servers, by job
Grouped by the job the tool does in the funnel. Official means the vendor runs the server or Anthropic ships the connector; posture is what the server lets Claude do, in the vendor's own terms.
01 · CRM
| Server | What Claude can do with it | Posture | Official status |
|---|---|---|---|
| HubSpotIntegration guide → | Answer pipeline questions, draft follow-ups from deal history, score and route inbound, and write approved updates back to contacts and deals. | Read + write (writes gated) | Official connector in the Claude apps and Claude Code |
| SalesforceIntegration guide → | Read opportunities, accounts, and activity under your own profile; draft and, with approval, update records and log activity. | Read + write (writes gated) | Official connector in the Claude apps and Claude Code |
02 · Data & enrichment
| Server | What Claude can do with it | Posture | Official status |
|---|---|---|---|
| Apollo.ioIntegration guide → | Search people and companies, enrich contacts, create or update records, and add prospects to sequences from a chat. | Read + write (search, enrich, create and update contacts, enroll in sequences; writes gated) | Official hosted server, native Claude connector, Claude Code plugin |
| ZoomInfoIntegration guide → | Search and enrich contacts and companies with ZoomInfo data and signals; writes land in your CRM, credits apply. | Read + enrich (credits apply); writes go to your CRM | Official hosted server (mcp.zoominfo.com), native connector, Claude Code plugin |
| FullEnrichIntegration guide → | Waterfall-enrich emails and mobiles for a person or a batch, preview results free, export to CSV or JSON on confirmation. | Read + enrich (credits spent only on confirmed exports) | Official hosted server (mcp.fullenrich.com) |
03 · Conversation intelligence
| Server | What Claude can do with it | Posture | Official status |
|---|---|---|---|
| GongIntegration guide → | Pull the last call with an account, its transcript and trackers, and turn it into a follow-up, a CRM note, or coaching. | Read (transcripts + deal data); writes go to your CRM, not Gong | Official connector in the Claude apps and Claude Code |
| FirefliesIntegration guide → | Read transcripts, summaries, and action items from recorded meetings; draft the recap and the CRM update from them. | Read (transcripts, summaries, action items); writes go to your CRM and inbox, not Fireflies | Official hosted server, listed in the Claude connector directory |
| DocketIntegration guide → | Query your website agent's conversations: which accounts asked what, extracted pain points, and agent performance, read-only. | Read only (agents, accounts, visitors, conversations); actions happen in your CRM | Official Demand MCP for Claude and ChatGPT |
04 · Sequencing
| Server | What Claude can do with it | Posture | Official status |
|---|---|---|---|
| OutreachIntegration guide → | Read prospects, accounts, sequences, tasks, and call intelligence; create sequences, tasks, prospects, and enrollments with confirmation. | Read + create (writes gated); the official server has no update tools yet | Official hosted server (api.outreach.io/mcp), in the connector directory |
| SalesloftIntegration guide → | Read cadence and activity data plus Clari call intelligence and forecast, with gated write-back into cadences. | Read (cadences, activity, calls, forecast) + write-back (gated) | Official server, native Claude listing |
05 · Comms & approvals
| Server | What Claude can do with it | Posture | Official status |
|---|---|---|---|
| SlackIntegration guide → | Read the channels you can read, summarize threads, and post digests or approval requests where you allow it. | Read channels + post messages (sends gated where they reach people) | Official connector in the Claude apps and Claude Code |
| Gmail ↗ | Search the inbox in plain language, read threads, label messages, and write drafts that land in your Drafts folder for you to send. | Read + draft | Anthropic Google Workspace connector |
| Google Calendar ↗ | Find open times, create and update events, RSVP, and add Meet links, so the follow-up meeting gets booked from the same chat as the recap. | Read + write | Anthropic Google Workspace connector |
06 · Knowledge
| Server | What Claude can do with it | Posture | Official status |
|---|---|---|---|
| NotionIntegration guide → | Search, read, and update the pages and databases you can access: playbooks, battlecards, meeting notes, the GTM wiki. | Read + write (writes gated to a drafts area first) | Official hosted server (mcp.notion.com) |
| Google Drive ↗ | Find, read, and cross-reference decks, docs, and sheets; save what Claude generates into a folder you pick. It cannot edit or move existing files. | Read + create | Anthropic Google Workspace connector |
| Atlassian (Jira, Confluence) ↗ | Read and update issues and pages under your own permissions: RevOps tickets, enablement docs, the launch checklist Confluence holds. | Read + write | Official Atlassian Rovo MCP server (mcp.atlassian.com) |
| Linear ↗ | Find, create, and update issues, projects, and comments, useful when GTM requests to product or ops run through Linear. | Read + write | Official hosted server (mcp.linear.app) |
07 · Infrastructure
| Server | What Claude can do with it | Posture | Official status |
|---|---|---|---|
| Stripe ↗ | Read customers, subscriptions, invoices, and balance for renewal and expansion briefs; can also create refunds and payment links, so gate it hard. | Read + write (moves money) | Official hosted server (mcp.stripe.com) |
| Supabase (Postgres) ↗ | Query the product database directly for usage and account data that never made it to the CRM; run SQL, inspect tables, read logs. | Read + write (SQL) | Official remote server with OAuth |
| Snowflake ↗ | Ask the warehouse questions through Cortex Analyst and Search, or run SQL under your default role, for pipeline and attribution data. | Read (SQL under your role) | Snowflake-managed server, public preview |
| Zapier ↗ | Reach the long tail: thousands of apps behind one server, each action you expose becoming a tool. The bridge for a vendor with no server of its own. | Read + write, per action you enable | Official hosted Zapier MCP |
Worth knowing: tools with no official server yet
LinkedIn has no public MCP server and a partner-gated API, so the honest paths are the Ads API for paid, exports and enrichment for research, and Claude drafting posts you publish yourself; the LinkedIn guide covers each. Clay's own path is Claude running inside a Clay table as the reasoning step, which for most list work beats a server anyway. If a vendor you rely on is missing, ask them for an official server before you accept a community wrapper.
GTM MCP servers: common questions
What is an MCP server, in GTM terms?
A small service a vendor runs that exposes its data and actions to an AI as tools: read this deal, pull that transcript, create a task. Claude connects to it with your login and can then work inside that system from a chat or a scheduled run, with no export or copy-paste in between.
Are MCP servers and Claude connectors the same thing?
Yes. The Claude apps present them as connectors in Settings, and Claude Code adds them as MCP servers from the command line, but it is one protocol and usually one server per vendor. A connection you make in one surface serves the other.
Which MCP servers should a sales team connect first?
The CRM, because every other play reads or writes to it, then the call recorder, because transcripts are the richest input Claude gets, then Slack, because that is where the output needs to land. Enrichment and sequencing come next once the read-write pattern is trusted.
Is it safe to let Claude write to these systems?
With guardrails, yes. Every connection inherits your own permissions, so Claude cannot reach further than you can. Allow reads freely, keep writes behind an approval until you trust the pattern, and treat the servers that can move money or email customers as the strictest tier.
Why are community MCP servers left off this list?
They lag the vendor's API, they break without notice, and handing one your CRM login is a security decision you should not make casually. Every row here is a server the vendor runs or a connector Anthropic ships, checked against the vendor's own documentation.