apollo-io

The Apollo.io MCP Server exposes Apollo.io's sales intelligence SDKs and data through the MCP interface, enabling AI agents and MCP clients to search leads, enrich profiles, manage CRM objects, and orchestrate outreach with a large suite of tools. After you wire up the server in your MCP client, you can invoke the 45+ tools directly in natural language prompts, leveraging Apollo’s database of companies, people, and activities. Start by ensuring your Apollo API key is configured, then use tools like search_people for prospecting, enrich_person for contact enrichment, and get_contact or search_contacts for CRM retrieval. The server also provides capabilities to manage deals, tasks, notes, labels, and sequences, allowing end-to-end workflow from lead discovery to outreach tracking via plain-language commands. Costs for each tool are surfaced in the tool descriptions, so you can plan usage alongside your credits.

To run locally, point your MCP client at the node server entry point and provide your API key. On Claude Code or Cursor, you specify the server under your mcpServers mapping and set the APOLLO_API_KEY environment variable. Once connected, you can issue queries like: find CTOs at Series B fintechs in NYC, enrich_contact for a given profile, or create_opportunity with related contacts, all through natural language prompts.

Prerequisites:

• Node.js 18+ and npm (or yarn)
• Access to Apollo.io API with a valid API key
• Git

Install and build steps:

1. Clone the repository

git clone https://github.com/Chainscore/apollo-io-mcp.git
cd apollo-io-mcp

2. Install dependencies

npm install

3. Build the MCP server package

npm run build

4. Prepare your API key (get it from Apollo.io settings) and test the server import path

• Create or update your MCP client configuration with the server entry and API key
• The server expects the entry point at dist/index.js after the build

5. Run the server locally (example)

node dist/index.js

6. Connect an MCP client (Claude Code, Cursor, etc.) using the following sample configuration (env var included in example)

{
  "mcpServers": {
    "apollo-io": {
      "command": "node",
      "args": ["/path/to/apollo-io-mcp/dist/index.js"],
      "env": {
        "APOLLO_API_KEY": "your_key_here"
      }
    }
  }
}

Notes and tips:

• Ensure your APOLLO_API_KEY is kept secret and not checked into version control.
• Use health_check or get_api_usage_stats (free tools) first to verify your API key is valid and your credits are sufficient.
• The server lists 45+ tools with distinct credit costs; plan usage to optimize credits.
• When testing locally, direct path to the built dist/index.js must be accurate; adjust "/path/to/apollo-io-mcp/dist/index.js" accordingly.
• If you update code, rebuild before restarting the MCP server to pick up changes.
• Some tools may require additional permissions or domain access on Apollo.io; review API capabilities in Apollo.io docs if you encounter access issues.