Apollo.Io MCP Server

Apollo.io MCP server for prospecting, enrichment, CRM, sequences, and outreach workflows. That is what the apollo.io mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A Model Context Protocol (MCP) server for the Apollo.io API -- giving AI coding assistants like Claude Code, Cursor, and any MCP-compatible client direct access to Apollo.io's sales intelligence platform.

• AI-native prospecting — -- Ask your AI assistant to "find CTOs at Series B fintech companies in NYC" and get results instantly
• Automated enrichment — -- Enrich leads with verified emails and phone numbers without leaving your editor
• CRM operations — -- Create, update, search, and delete contacts, accounts, deals, tasks, and notes through conversation
• Sequence management — -- Add contacts to email sequences and monitor outreach performance
• Full pipeline visibility — -- Access contact stages, account stages, opportunity stages, labels, and team members
• Credit-aware — -- Every tool description includes credit cost so your AI avoids unexpected charges

Getting it running

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 5 tools. What each one is for:

• Auto — cleaned domains** -- Pass https://www.google.com, www.google.com, or @google.com -- all resolve to google.com
• Built — in deduplication** -- Contact creation enforces dedup so you never accidentally create duplicates
• search_news_articles — Search recent news about target companies
• get_api_usage_stats — Check API credit usage and remaining balance
• health_check — Verify API key and check Apollo API health

What it needs from you

Configuration is passed through the environment: APOLLO_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 18+ - Apollo.io API key (get one here) - An MCP-compatible client (Claude Code, Cursor, etc.)

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Apollo.Io's toolset — Auto, Built, search_news_articles and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Inferensys; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.