概览
What is Apollo.io MCP Server?
A Model Context Protocol (MCP) server that integrates with the Apollo.io API, enabling AI assistants to enrich people and organization data, search for contacts and companies, and find job postings directly through natural language commands.
How to use Apollo.io MCP Server?
Clone the repository, run npm install and npm build, then start the server with npm start. Provide your Apollo.io API key via the APOLLO_IO_API_KEY environment variable or the --api-key command-line argument. For an SSE server with authentication, use npx mcp-proxy-auth node dist/index.js.
Key features of Apollo.io MCP Server
- Enrich data for a single person by name or email
- Enrich data for a single organization by domain or name
- Search for people by title, seniority, or company domain
- Search for organizations by domain or location
- Find job postings for a specific Apollo.io organization ID
Use cases of Apollo.io MCP Server
- Enrich contact records with up-to-date Apollo.io data from within an AI assistant
- Search for people matching specific job titles and seniority levels across organizations
- Look up company details and job postings without leaving the AI interface
- Automate prospecting workflows by piping Apollo.io data into downstream tools
FAQ from Apollo.io MCP Server
What exactly does Apollo.io MCP Server do?
It exposes five tools—people enrichment, organization enrichment, people search, organization search, and organization job postings—that let AI assistants read and query Apollo.io data.
How do I authenticate with the Apollo.io API?
Generate an API key in your Apollo.io account under Settings > API, then provide it either as the APOLLO_IO_API_KEY environment variable or as the --api-key command-line argument.
What runtime or dependencies are required?
The server is built with TypeScript (4.9.5) and the MCP SDK (1.8.0). You need Node.js and npm installed to clone, install dependencies, and build the project.
Can I run it as an SSE server with authentication?
Yes. Use the mcp-proxy-auth package by setting AUTH_SERVER_URL to your verification endpoint and running npx mcp-proxy-auth node dist/index.js. The SSE endpoint is then available at localhost:8080/sse?apiKey=apikey.
How is this server different from using the Apollo.io API directly?
It translates natural language commands from AI assistants into structured Apollo.io API calls, removing the need to manually construct HTTP requests or handle authentication inside the assistant.
