Apollo.io MCP server icon

Apollo.io

by Apollo.io

Sales & CRM13 tools

Search a 240M-contact B2B database, reveal work emails and direct-dial numbers, and enrol prospects into automated outreach sequences from Claude or ChatGPT. Anthropic's listing names 13 tools; Apollo's developer docs enumerate 52. Enrolment into an active sequence starts outreach on the sequence schedule, from your own connected mailbox.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Apollo.io via MCP

https://mcp.apollo.io/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Apollo.io Tools & Capabilities (13)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Enrolling a contact in an active sequence starts outreach. Apollo states enrolment places eligible contacts at step one on the sequence sending schedule. The human gate is sequence activation, which happens before enrolment — against a workspace with live sequences, that gate has already been passed.
  • The mail comes from your own mailbox, not an Apollo domain. Deliverability, domain reputation and the sender's name on a cold email are all yours.
  • Removal only stops pending outreach. Apollo states removal deletes pending steps and keeps activity history. Delivered email cannot be recalled. Removal is not shown as a status, and re-adding restarts at step one.
  • Enrolling someone already in another sequence compounds outreach. Apollo states such a contact receives messaging from every sequence they are in. Validation warns; it does not block.
  • Enrichment returns third-party contact details. Work email, employment history and, on request, personal emails and mobile numbers for people who did not supply them to you. Apollo publishes its data-broker status and its collection sources; this page takes no legal position.
  • Credits: 1–9 per person enriched, and up to 10 people per bulk call — up to 90 credits in a single tool call. Bulk people enrichment allows 600 calls per hour.
  • Waterfall enrichment has no published per-person cap. Apollo states cost depends on your configured vendors and that some charge per lookup even when nothing is found. Waterfall responses omit credits_consumed entirely rather than reporting zero.
  • The two credit tables do not fully agree on sequence enrolment. The MCP action table says adding contacts to a sequence is free; the enrolment documentation states one credit per net-new verified contact (both fetched 2026-08-19).
  • The directory listing names 13 tools; Apollo documents 52 actions. Do not treat the listing as an inventory. Apollo states availability varies by plan, permissions, client and rollout.
  • Sixty-seven OAuth scopes are advertised — far more than 13 tools need, including scopes for buying sending domains and mailboxes. app_scopes is undocumented as to breadth.
  • Free plans connect but are heavily limited. Database prospecting, bulk enrichment and company search need a paid plan, and a work email address is mandatory.
  • Rate limits are per team, per endpoint, in three windows at once. Apollo publishes free-plan ceilings of 50 requests/minute, 200/hour and 600/day, against 200/minute and up to 6,000/day on Organization plans, with enrichment and search endpoints on separate higher tiers for paid plans.
  • No delete tool exists. Apollo states destructive bulk operations such as bulk delete and unrestricted bulk update are not supported — a deliberate cap this page credits, while noting it also means the connector cannot remove a record it created.
  • Enrichment results are not saved automatically. Apollo warns that data returned to the chat is not stored as an Apollo contact and will not appear in later Apollo exports unless separately saved — so revealed contact details may live only in your AI client's transcript.
  • Model training must be off. Apollo prohibits it for MCP integrations and requires you to confirm the setting before connecting.
  • Apollo logs MCP requests and responses, per its privacy policy, for security, abuse prevention, troubleshooting and service quality.
  • The integration is per-user, not per-workspace. Each person sets it up separately, so there is no admin-level view of who has connected.
  • We could not verify tool behaviour ourselves. The endpoint returns 401 anonymously, so no inputSchema and no readOnlyHint or destructiveHint annotations were readable. No tool was called and no authentication was attempted. Every capability claim here comes from Apollo's documentation, its live OAuth metadata, or Anthropic's listing.
  • Prompts are unconfirmed. Anthropic's snapshot lists no prompt names.

Frequently asked questions

Does adding a contact to an Apollo sequence through MCP start sending email?

Yes, if the sequence is already active. Apollo states that adding contacts to an active sequence enrols eligible contacts at step one according to the sequence sending schedule, so automated email steps go out on that schedule without a further human press. The human gate is sequence activation, which happens before enrolment, not at it.

Whose mailbox does Apollo MCP send sequence emails from?

Your own connected mailbox, not an Apollo sending domain. Apollo requires at least one linked mailbox before contacts can be enrolled, and you choose which mailbox at enrolment time. Multiple mailboxes can be rotated to spread volume. Recipients see a real person's address, so deliverability and reputation land on your domain.

What does removing a contact from an Apollo sequence actually undo?

Only future steps. Apollo states that removing selected contacts from a sequence deletes their pending outreach, and keeps the contact's activity history. Email already delivered cannot be recalled by any tool on this connector. Removal corrects a wrong enrolment going forward; it does not reach messages that already left your mailbox.

How many tools does the Apollo MCP server have?

Anthropic's 2026-08-16 directory snapshot names 13. Apollo's own developer documentation enumerates 52 available actions covering deals, lists, custom objects, conversation intelligence, tasks and analytics that the listing omits entirely. The 13 named tools are a narrow, coherent subset of a much wider REST API, which is a deliberate-looking restraint rather than a documentation gap.

How many credits does Apollo MCP enrichment cost?

Apollo documents 1 to 9 credits per person without waterfall enrichment: one credit for demographics or an email address, plus eight more if a mobile phone number is returned. No match means zero credits. Bulk people enrichment caps at ten people per request, so a single call can consume up to ninety credits.

Which OAuth scopes does the Apollo MCP server request?

Sixty-seven named scopes, verified live on 2026-08-19 in Apollo's RFC 9728 descriptor. Sequence enrolment sits behind its own scope, distinct from the search and enrichment scopes, so a client could in principle grant prospecting without outreach. The scope vocabulary is far wider than the 13 listed tools require.

Can you use the Apollo MCP server on a free Apollo plan?

Yes, with real restrictions. Apollo states MCP is available on all plans including free, and that free accounts can search saved contacts, enrich individual people, add contacts to sequences and view connected mailboxes. Database prospecting, bulk enrichment and company search need a paid plan. Free accounts must register with a work email address.

Sources

  • Integrate Apollo with Claude — https://knowledge.apollo.io/hc/en-us/articles/43827318678541-Integrate-Apollo-with-Claude (fetched 2026-08-19; this is the page Anthropic's documentation URL resolves into. Beta status, the work-email requirement, the model-training prohibition, per-action always-allow / approval-required / blocked permission levels, the user-specific setup note, the enrich-after-search and list-mailboxes-before-enrolling best practices, and the warning that enrichment results are not saved as Apollo contacts) · retrieved 2026-08-19
  • Apollo MCP developer documentation — https://docs.apollo.io/docs/apollo-mcp (fetched 2026-08-19; the 240M+ database figure, the endpoint and transport table, client configurations for five families, the 52-action availability table with per-action credit flags, the limitations list including unsupported bulk delete, and the privacy section) · retrieved 2026-08-19
  • Use Apollo with AI Tools to Run Your GTM Workflow — https://knowledge.apollo.io/hc/en-us/articles/45119679436557-Use-Apollo-with-AI-Tools-to-Run-Your-GTM-Workflow (fetched 2026-08-19; the customer-facing 24-action credit table, the free-plan capability split, the ~25-results-per-page figure, the statement that searches exclude emails and phone numbers, and the answer that destructive bulk operations are unsupported) · retrieved 2026-08-19
  • Add Contacts to a Sequence — https://knowledge.apollo.io/hc/en-us/articles/4409396985741-Add-Contacts-to-a-Sequence (fetched 2026-08-19; the decisive statement that enrolment into an active sequence starts contacts at step one on the sequence sending schedule, the linked-mailbox prerequisite, mailbox rotation and capacity assignment, enrolment validation warnings, scheduled enrolment, individual-not-group sends, and the one-credit-per-net-new-verified-contact charge) · retrieved 2026-08-19
  • Manage Contacts in a Sequence — https://knowledge.apollo.io/hc/en-us/articles/46681725112589-Manage-Contacts-in-Sequences (fetched 2026-08-19; removal deletes pending outreach and keeps activity history, pause and resume semantics, the absence of a "Removed" status, and re-adding restarting at step one) · retrieved 2026-08-19
  • Sequences Overview — https://knowledge.apollo.io/hc/en-us/articles/4409237165837-Sequences-Overview (fetched 2026-08-19; the definition of a sequence as an automated multichannel outreach campaign, the activate-then-enrol build order, multi-sequence enrolment compounding messaging, prospect-score prioritisation, and out-of-office auto-pause in seven named languages) · retrieved 2026-08-19
  • People Enrichment — https://docs.apollo.io/reference/people-enrichment (fetched 2026-08-19; the 1–9 credits per person rate and its 1 + 8 breakdown, zero credits on no match, the people_match scope, the work-email requirement for free accounts, response fields, reveal_personal_emails and reveal_phone_number, and the waterfall webhook flow) · retrieved 2026-08-19
  • Bulk People Enrichment — https://docs.apollo.io/reference/bulk-people-enrichment (fetched 2026-08-19; the 10-people-per-request cap and its record_limit_exceeded error, the documented 600-calls-per-hour ceiling, and the note that waterfall responses omit credits_consumed and missing_records entirely rather than returning zero) · retrieved 2026-08-19
  • Rate Limits — https://docs.apollo.io/reference/rate-limits (fetched 2026-08-19; limits are per team, per endpoint and enforced in three windows at once; free-plan 50/minute, 200/hour, 600/day against Organization 200/minute and 6,000/day, with separate enrichment and search tiers) · retrieved 2026-08-19
  • Apollo Privacy Policy — https://www.apollo.io/privacy-policy (last updated 2026-08-10, fetched 2026-08-19; the dedicated "Agentic workflows and the MCP server" clause — MCP request logging, suppression-list exclusion from MCP responses, authentication and permission scoping, and customer responsibility for lawful use; plus the registered-data-broker self-description, the collection-sources list, the categories made available to customers, the sale-and-sharing disclosure, and the access, deletion, correction and opt-out routes) · retrieved 2026-08-10
  • knowledge.apollo.io/robots.txt (fetched 2026-08-19) — a stock Zendesk policy with no Content-Signal directives on any axis; it disallows article view-stat API paths but permits the documented Help Center article JSON API used here. knowledge.apollo.io/llms.txt returns 404. Method note: on this Zendesk host the .md suffix is ignored and serves HTML, so every help-centre article above was read through /api/v2/help_center/en-us/articles/<id>.json · retrieved 2026-08-19
  • www.apollo.io/robots.txt (fetched 2026-08-19) — no Content-Signal directives, but explicit named allowances for anthropic-ai, ClaudeBot, GPTBot, ChatGPT-User and cohere-ai. docs.apollo.io/robots.txt allows crawling, names a sitemap, and points at docs.apollo.io/llms.txt, a 10 KB machine index; that host serves clean Markdown when .md is appended, which is how the developer pages above were read · retrieved 2026-08-19
  • Live anonymous probe — 2026-08-19: an initialize call to https://mcp.apollo.io/mcp returns HTTP 401 with a JSON body naming a missing Authorization header, and a www-authenticate header carrying resource_metadata plus all 67 scopes inline — authoritative under RFC 9728. No tool was called and no authentication was attempted · retrieved 2026-08-19
  • Live RFC 9728 protected-resource descriptor — https://mcp.apollo.io/.well-known/oauth-protected-resource (fetched 2026-08-19; 1,881 bytes, 67 scopes_supported, resource naming the /mcp path, header-only bearer_methods_supported, and an openid_configuration_endpoint). Root and path-append forms return byte-identical 200 bodies; the path-insert form under /mcp/ returns a zero-byte 404 · retrieved 2026-08-19
  • Live RFC 8414 authorization-server metadata — https://mcp.apollo.io/.well-known/oauth-authorization-server (fetched 2026-08-19; authorization_code, refresh_token and client_credentials grants, PKCE S256, client_secret_basic / client_secret_post / none, and present registration_endpoint and revocation_endpoint). Same three-form behaviour. The OpenID Connect discovery document is also served, adding jwks_uri, subject_types_supported and RS256 · retrieved 2026-08-19
  • Anthropic connector directory — https://claude.ai/directory/8fd555a4-ea5f-49cf-9335-582dd6760597 (snapshot 2026-08-16; 13 tool names, permissions of "Read and write", no prompt names, partner tier, one category, remote type, added 2026-02-20, and an oauth2 probe posture returning 401) · retrieved 2026-08-16
  • Apollo support — https://www.apollo.io/submit-a-request (listed by Anthropic's directory, not fetched)

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
Sales & CRM
Developer
Apollo.io
Tools
13
Domain
mcp.apollo.io

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.