Apollo.io MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APOLLO_IO_API_KEY | Yes | Your Apollo.io API access token obtained from Apollo.io Account > Settings > API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| people_enrichmentC | Use the People Enrichment endpoint to enrich data for 1 person |
| organization_enrichmentC | Use the Organization Enrichment endpoint to enrich data for 1 company |
| people_searchD | Use the People Search endpoint to find people |
| organization_searchC | Use the Organization Search endpoint to find organizations |
| organization_job_postingsC | Use the Organization Job Postings endpoint to find job postings for a specific organization |
| get_person_emailC | Get email address for a person using their Apollo ID |
| employees_of_companyC | Find employees of a company using company name or website/LinkedIn URL |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose targeting specific Apollo.io API endpoints: employees_of_company finds employees, get_person_email retrieves emails, organization_enrichment and people_enrichment enrich data, organization_job_postings finds job postings, and organization_search and people_search perform searches. There is no overlap in functionality, making tool selection unambiguous.
The tools follow a consistent snake_case naming convention, but the pattern is not fully uniform: most use a verb_noun structure (e.g., organization_search, people_enrichment), while employees_of_company and get_person_email deviate slightly in phrasing. Overall, naming is readable and mostly predictable with minor inconsistencies.
With 7 tools, the server is well-scoped for its purpose of accessing Apollo.io's data enrichment and search APIs. Each tool serves a specific function, covering key operations like searching, enriching, and retrieving data for organizations and people, without being overly sparse or bloated.
The tool set provides comprehensive coverage for core Apollo.io use cases, including search and enrichment for both organizations and people, plus specific utilities like email retrieval and job postings. A minor gap exists in lacking update or deletion tools, but this is reasonable given the API's likely read-only nature, and agents can work effectively with the provided operations.