Apollo.io MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APOLLO_API_KEY | Yes | Your Apollo.io API key for authentication |
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 |
|---|---|
| search_peopleB | Search for people/contacts in Apollo's database with advanced filters. Use this to find prospects, leads, or specific individuals based on criteria like job title, company, location, industry, seniority, etc. |
| search_organizationsA | Search for companies/organizations in Apollo's database. Filter by industry, size, location, revenue, technology, and more. Great for building targeted account lists. |
| enrich_personB | Enrich a person's data with email, phone, social profiles, employment info, and more. Provide either email, name+domain, or LinkedIn URL. |
| enrich_organizationC | Enrich an organization's data with detailed company information, employee count, revenue, technologies used, funding, and more. Provide domain name. |
| find_emailC | Find and verify email addresses for a person. Provide name and company domain or LinkedIn URL. |
| list_sequencesC | List all email sequences in your Apollo account. Sequences are automated email campaigns. |
| get_sequenceC | Get detailed information about a specific sequence including steps, stats, and settings. |
| analyze_sequenceC | Analyze a sequence's performance with detailed metrics: open rates, reply rates, bounce rates, contacts added, active contacts, and step-by-step analytics. |
| add_to_sequenceC | Add contacts to a sequence. Provide sequence ID and contact email addresses or contact IDs. |
| remove_from_sequenceC | Remove contacts from a sequence. Provide sequence ID and contact IDs. |
| get_listsB | Get all contact lists in your Apollo account. Lists are collections of saved contacts. |
| get_list_contactsC | Scrape/retrieve all contacts from a specific list with full details including emails, titles, companies, etc. |
| analyze_listB | Analyze a contact list with detailed breakdown: total contacts, job titles distribution, seniority levels, companies, locations, industries, and data completeness metrics. |
| create_contactC | Create a new contact in Apollo with details like name, email, title, company, etc. |
| update_contactC | Update an existing contact's information in Apollo. |
| create_accountC | Create a new account/organization in Apollo with company details. |
| get_accountC | Get detailed information about an account/organization by ID or domain. |
| search_job_postingsC | Search for job postings to identify companies that are hiring and find buying signals. |
| get_person_activityC | Get activity history and engagement data for a specific person/contact. |
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 19 tools
Most tools have clearly distinct purposes targeting different resources (e.g., contacts, sequences, organizations) and actions (e.g., create, get, search, analyze). However, some overlap exists between 'analyze_list' and 'get_list_contacts' (both involve list data retrieval), and 'enrich_person' and 'find_email' (both relate to person data enrichment), which could cause minor confusion.
Tool names follow a consistent verb_noun pattern throughout (e.g., 'create_contact', 'search_people', 'analyze_sequence'), with clear and readable conventions. There are minor deviations like 'get_lists' (plural) versus 'get_sequence' (singular), but overall, the naming is highly predictable and well-structured.
With 19 tools, the count is slightly high but reasonable for a comprehensive sales/CRM platform like Apollo.io, covering contacts, sequences, organizations, and analytics. It avoids being overwhelming (e.g., not exceeding 25) and provides broad functionality without obvious bloat, though it could be streamlined slightly.
The toolset offers complete CRUD/lifecycle coverage for the domain: create, get, update, and delete (implied via removal) for contacts and sequences, plus enrichment, search, and analytics tools. There are no obvious gaps; agents can perform end-to-end workflows from prospecting to engagement analysis without dead ends.