Apollo MCP: The Official Server, and What It Can't Do
Yes — Apollo.io has an official MCP server. It’s a first-party connector, not a community project, and it’s built to work with Claude, ChatGPT, and Perplexity out of the box. (Quick disambiguation: this is Apollo.io, the sales intelligence and prospecting platform — not Apollo GraphQL, which ships an unrelated MCP server for GraphQL APIs.) If you’re searching “Apollo MCP” to prospect faster, the connection you want already exists.
The thing worth knowing before you set it up: an MCP server hands your Apollo account to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches your pipeline for you, nothing fires when a lead replies, and nothing runs while the chat is closed. Here’s exactly what the Apollo MCP does, how to turn it on, where it stops — and what to use when you want Apollo work that runs on its own.
Apollo is one of many — the complete list of MCP servers covers every app that ships one, grouped by category.
What the Apollo MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, and others — talk to an outside app through a shared interface. Apollo’s official server sits at mcp.apollo.io/mcp and connects over Streamable HTTP with OAuth, so it works with either Apollo’s first-party connectors inside ChatGPT, Claude, and Perplexity, or any other MCP-compatible client that supports remote servers.
Once it’s connected, an AI client can reach into Apollo’s 240M+ contact database and your own account data to:
- Search prospects and companies — “find heads of RevOps at US B2B SaaS companies with 50–200 employees” answered against live data, not a guess.
- Enrich records — fill in verified emails, titles, and firmographic data for a single contact or a whole list at once.
- Manage contacts and sequences — create or update contacts, search sequences, add or remove people from them, and check which email accounts are sending.
- Send and report — fire off a one-off email, hand off a task, or pull analytics on how a sequence is performing.
It’s genuinely useful for ad-hoc prospecting: ask for a list, enrich it, load it into a sequence, all from one conversation.
How to set up the Apollo MCP server
Apollo built this for non-technical setup — no API key or developer config required for the first-party path:
- In Claude, ChatGPT, or Perplexity, open the connectors/plugins directory and find Apollo.
- Authorize it against your Apollo account through the OAuth prompt — any plan works, including the free tier, since MCP access mirrors your existing account permissions.
- Start a chat and ask it to search, enrich, or sequence — the same credits your Apollo plan already meters (enrichment draws credits; search and contact management typically don’t).
If your AI client isn’t one of the three first-party integrations, point it at the remote endpoint mcp.apollo.io/mcp directly — it accepts any MCP client that supports Streamable HTTP with OAuth, including Claude Code, Claude Desktop, and VS Code with GitHub Copilot.
Where the Apollo MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch your pipeline; it waits for you to ask.
- No triggers. A lead replying, a sequence finishing, a contact getting enriched — none of these can start anything through MCP. There’s no “when this happens in Apollo, do that.”
- It’s one app at a time. The Apollo MCP knows Apollo. Getting a replied lead into your CRM, a Slack alert to the rep, and a calendar hold for the call means wiring up a separate MCP server for each and hoping your client can juggle them in one turn.
- You own the plumbing and the scopes. OAuth tokens and the blast radius of an AI with write access to your prospect database and sequences are on you.
So the Apollo MCP is a great way to ask Apollo things and prospect on the spot. It is not a way to make Apollo run — to have work happen on a schedule or in reaction to an event, across the other tools a lead touches after Apollo hands it off.
Running Apollo work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Apollo natively — no MCP server to host, no OAuth plumbing to maintain — and to the ~260 other apps it supports, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Apollo work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a sequence reply comes in → pull the contact into your CRM, notify the rep in Slack, and draft a reply for approval — automatically, the moment it lands.
- Every morning → pull yesterday’s newly enriched leads, score them, and route the best ones to the right rep’s task list.
- When a deal closes → remove the contact from any active Apollo sequences and log the outcome back to the CRM, so no one gets a cold outbound email after they’ve already bought.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, scoring, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Apollo connection and everything downstream.
If you just want to prospect and enrich from a chat, Apollo’s official MCP server is the right tool and it costs nothing extra to connect. If you want Apollo to actually do things — on a trigger, on a schedule, across every app a lead flows through after Apollo — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Apollo.io have an official MCP server?
Yes. It’s a first-party server at mcp.apollo.io/mcp, with built-in connectors inside Claude, ChatGPT, and Perplexity, plus support for any other MCP client over Streamable HTTP with OAuth.
Is the Apollo MCP server free to connect? Yes — there’s no additional cost to connect. Your existing Apollo plan, permissions, and credits still apply, so enrichment actions still draw credits the way they would inside the app.
Can the Apollo MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Apollo work across apps, you need a workflow tool like Carly rather than an MCP server.
Is this the same as the Apollo GraphQL MCP server? No. Apollo.io (sales intelligence and prospecting) and Apollo GraphQL (the API platform) are unrelated companies that happen to share a name, and each ships its own separate MCP server. This page is about Apollo.io’s prospecting MCP.
Can I connect Apollo to AI without coding or hosting a server? Yes. You don’t have to touch MCP at all. Carly connects to Apollo for you and lets you build the automation in plain language — describe what you want to happen and it wires up the Apollo connection and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
