Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@apollo-io-mcp-server Find senior engineers at Google"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This project provides an MCP server that exposes the Apollo.io API functionalities as tools. It allows you to interact with the Apollo.io API using the Model Context Protocol (MCP).
The project consists of the following main components:
apollo_client.py: Defines the ApolloClient class, which is used to interact with the Apollo.io API. It includes methods for people enrichment, organization enrichment, people search, organization search, and organization job postings.
server.py: Defines the FastMCP server, which exposes the Apollo.io API functionalities as tools. It uses the ApolloClient class defined in apollo_client.py to interact with the API.
apollo/: Contains the data models for the Apollo.io API, such as PeopleEnrichmentQuery, OrganizationEnrichmentQuery, PeopleSearchQuery, OrganizationSearchQuery, and OrganizationJobPostingsQuery.
Related MCP server: Apollo.io MCP Server
The following functionalities are exposed as MCP tools:
people_enrichment: Use the People Enrichment endpoint to enrich data for 1 person.
organization_enrichment: Use the Organization Enrichment endpoint to enrich data for 1 company.
people_search: Use the People Search endpoint to find people.
organization_search: Use the Organization Search endpoint to find organizations.
organization_job_postings: Use the Organization Job Postings endpoint to find job postings for a specific organization.
To use this MCP server, you need to:
Set the APOLLO_IO_API_KEY environment variable with your Apollo.io API key. Or create '.env' file in the project root with APOLLO_IO_API_KEY.
Get dependencies: uv sync
Run the uv run mcp run server.py
The apollo/ directory contains the data models for the Apollo.io API. These models are used to define the input and output of the MCP tools.
apollo/people.py: Defines the data models for the People Enrichment endpoint.
apollo/organization.py: Defines the data models for the Organization Enrichment endpoint.
apollo/people_search.py: Defines the data models for the People Search endpoint.
apollo/organization_search.py: Defines the data models for the Organization Search endpoint.
apollo/organization_job_postings.py: Defines the data models for the Organization Job Postings endpoint.
To test, set APOLLO_IO_API_KEY environment variable and run uv run apollo_client.py.
Configure Claude for Desktop to use these MCP servers by adding them to your claude_desktop_config.json file:
{
"mcpServers": {
"apollo-io-mcp-server": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"mcp",
"run",
"path/to/apollo-io-mcp-server/server.py"
]
}
}
}Use the Organization Enrichment endpoint to enrich data for 1 company.
https://docs.apollo.io/reference/organization-enrichment
Inputs: query (required).
Use the Organization Job Postings endpoint to find job postings for a specific organization.
https://docs.apollo.io/reference/organization-jobs-postings
Inputs: organization_id (required).
Use the Organization Search endpoint to find organizations.
https://docs.apollo.io/reference/organization-search
Inputs: query (required).
Use the People Enrichment endpoint to enrich data for 1 person.
https://docs.apollo.io/reference/people-enrichment
Inputs: query (required).
Use the People Search endpoint to find people.
https://docs.apollo.io/reference/people-search
Inputs: query (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
Each tool targets a distinct entity and operation: organization enrichment, job postings, search; people enrichment and search. No overlapping purposes.
All tools use a consistent pattern of <entity>_<operation> in snake_case, with operations like enrichment, search, and job_postings.
With 5 tools covering the two main domains (organizations and people) and key operations (search and enrichment), the count is well-scoped.
The tool set provides search and enrichment for both entities, plus job postings for organizations. No obvious gaps for the intended sales intelligence use case.
Your agent needs B2B contacts and the pipeline objects around them — find the company, find the person, get the email, then write it back where your team works. **What you can ask for** • "Find heads of engineering at Series-B SaaS companies in the Nordics, with emails." • "Enrich these companies with headcount, industry and funding." • "What roles is this company hiring for right now?" • "Create an account and a contact, then log this opportunity." • "Search our sequences for messages sent to this domain." **How to use it** Point any MCP client at https://mcp.aisa.one/apollo/mcp and sign in with OAuth — there is no key to create or paste. 54 tools: people and organisation search and enrichment, job postings, accounts, contacts, opportunities and their stages, custom fields, labels, notes, users, email accounts, sequence messages and phone-call search — reads and writes. **Why this rather than the source** The full object model, not just a search endpoint, so an agent can finish the job rather than hand you a CSV. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the person here, then ask the same agent what their company's traffic looks like or what they rank for — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/sales/mcp adds Similarweb and creator discovery around it.
Apollo.io MCP — company and people data via api.apollo.io, the caller's OWN Apollo account (fleet…
Search people and companies, enrich profiles, and find email and phone over MCP.
Your agent needs a pipeline, not a list — the companies worth calling, the people who decide inside them, a way to reach those people, and the market evidence that the account is worth the call. **What you can ask for** • "Find Series-B fintech companies in Germany and the heads of marketing there, with emails." • "Enrich these 200 domains with headcount, funding and tech stack." • "Which of these accounts is hiring for roles that imply they need us?" • "How much traffic does this prospect get, and where does it come from?" • "Create the account and contact records and move this opportunity to the next stage." **How to use it** Point any MCP client at https://mcp.aisa.one/sales/mcp and sign in with OAuth — there is no key to create or paste. 79 tools: Apollo people and company search, enrichment, accounts, contacts, opportunities and stages, job postings, sequences and call activity; Similarweb traffic, audience, referrals, ad spend and competitors; plus creator discovery. **Why this rather than the source** Prospecting, enrichment, market sizing and the CRM writes behind one login instead of three. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Build the list here, then ask the same agent what those companies rank for or what is being said about them — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/apollo/mcp or https://mcp.aisa.one/similarweb/mcp for one of them alone; https://mcp.aisa.one/gtm/mcp adds the social side.
