Apollo MCP Server
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 MCP Server find marketing directors at SaaS companies in New York"
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.
Apollo MCP Server
A Model Context Protocol (MCP) server for Apollo.io - the leading sales intelligence and engagement platform. This server provides 34+ tools for automating sales outreach, prospecting, and pipeline management.
Features
People Search & Enrichment - Find and enrich contact data from Apollo's 275M+ contact database
Organization Search & Enrichment - Search companies by industry, size, location, and more
Email Sequences - Create and manage automated outreach campaigns with A/B testing
Contact Management - Organize contacts into lists and manage pipeline stages
Workflow Automation - Build event-driven automations for your sales process
Tasks & Activities - Create and track sales activities
Deals Pipeline - Manage opportunities through your sales pipeline
Analytics - Track sequence performance and email deliverability
Related MCP server: Apollo.io MCP Server
Installation
Prerequisites
Install with uv
# Clone the repository
git clone https://github.com/BlockchainRev/apollo-mcp-server.git
cd apollo-mcp-server
# Install dependencies
uv pip install -e .Install with pip
pip install -e .Configuration
Get Your Apollo API Key
Log in to Apollo.io
Go to Settings > Integrations > API
Generate or copy your API key
Set Environment Variable
export APOLLO_API_KEY="your-api-key-here"Or add to your shell profile (~/.bashrc, ~/.zshrc, etc.):
echo 'export APOLLO_API_KEY="your-api-key-here"' >> ~/.zshrcUsage
With Claude Code
Add to your Claude Code MCP configuration (~/.claude.json):
{
"mcpServers": {
"apollo": {
"command": "uv",
"args": ["run", "--directory", "/path/to/apollo-mcp-server", "python", "-m", "apollo_mcp.server"],
"env": {
"APOLLO_API_KEY": "your-api-key-here"
}
}
}
}Standalone
# Run the server
python -m apollo_mcp.serverAvailable Tools
People & Contacts (6 tools)
Tool | Description |
| Search Apollo's 275M+ contact database with filters |
| Enrich a person's profile by email, name, or LinkedIn |
| Search contacts in your Apollo CRM |
Organizations (3 tools)
Tool | Description |
| Search companies by industry, size, location |
| Get comprehensive company data by domain |
| Get current job postings for a company |
Email Sequences (5 tools)
Tool | Description |
| List all email sequences |
| Get sequence details and stats |
| Create multi-step outreach sequences |
| Add contacts to a sequence |
| Activate or pause a sequence |
Contact Lists (3 tools)
Tool | Description |
| Get all saved lists |
| Create a new contact list |
| Add contacts to a list |
Workflows (7 tools)
Tool | Description |
| List all workflow automations |
| Get workflow details |
| Create event-driven automations |
| Update workflow configuration |
| Activate or deactivate workflows |
| Delete a workflow |
| Browse workflow templates |
| Create from a template |
Email (2 tools)
Tool | Description |
| Preview emails with variable substitution |
| Send one-off emails |
Tasks (2 tools)
Tool | Description |
| List all tasks |
| Create tasks for contacts |
Deals (2 tools)
Tool | Description |
| List pipeline opportunities |
| Create new deals |
Analytics (2 tools)
Tool | Description |
| Get sequence performance metrics |
| Get email deliverability stats |
Utility (4 tools)
Tool | Description |
| List email personalization variables |
| Get sending schedule options |
| Get contact pipeline stages |
| Get account pipeline stages |
Examples
Search for Decision Makers
# Find VPs of Sales at tech companies in California
people_search(
person_titles=["VP Sales", "Vice President of Sales"],
organization_locations=["California, US"],
organization_num_employees_ranges=["51,200", "201,500"]
)Create an Outreach Sequence
sequence_create(
name="New Lead Outreach",
steps=[
{
"type": "auto_email",
"wait_time": 0,
"wait_mode": "minute",
"emailer_touches": [{
"type": "new_thread",
"subject": "Quick question about {{company}}",
"body_html": "<p>Hi {{first_name}},</p><p>I noticed {{company}} is growing...</p>"
}]
},
{
"type": "auto_email",
"wait_time": 3,
"wait_mode": "day",
"emailer_touches": [{
"type": "reply",
"subject": "Re: Quick question about {{company}}",
"body_html": "<p>Following up on my last email...</p>"
}]
}
]
)Create a Workflow Automation
workflow_create(
name="New Contact Nurture",
trigger_type="event",
trigger_events=["contact_saved_or_created"],
actions=[
{"type": "add_to_sequence", "config": {"sequence_id": "abc123"}}
]
)Email Personalization Variables
Use these variables in email templates:
Variable | Description |
| Contact's first name |
| Contact's last name |
| Company name |
| Job title |
| Email address |
| City |
| State/region |
| Country |
API Endpoints
The server uses two Apollo API endpoints:
Public API (
api.apollo.io/v1/): People search, enrichmentApp API (
app.apollo.io/api/v1/): Sequences, workflows, lists, etc.
All requests use the X-Api-Key header for authentication.
Development
Project Structure
apollo-mcp-server/
├── apollo_mcp/
│ ├── __init__.py # Package initialization
│ ├── server.py # Main MCP server
│ ├── client.py # HTTP client for Apollo API
│ ├── utils/
│ │ ├── __init__.py
│ │ ├── config.py # Configuration and settings
│ │ └── formatting.py # Output formatting utilities
│ └── tools/
│ ├── __init__.py # Tool registration
│ ├── people.py # People/contact tools
│ ├── organizations.py # Organization tools
│ ├── sequences.py # Email sequence tools
│ ├── lists.py # List management tools
│ ├── workflows.py # Workflow automation tools
│ ├── email.py # Email tools
│ ├── tasks.py # Task management tools
│ ├── deals.py # Deal/opportunity tools
│ ├── analytics.py # Analytics tools
│ └── utility.py # Helper tools
├── examples/
│ └── basic_usage.py # Usage examples
├── pyproject.toml # Project configuration
├── requirements.txt # Dependencies
└── README.mdRunning Tests
# Install dev dependencies
uv pip install -e ".[dev]"
# Run tests
pytestContributing
Contributions are welcome! Please:
Fork the repository
Create a feature branch
Make your changes
Submit a pull request
License
MIT License - see LICENSE for details.
Acknowledgments
Available Tools
34 toolsanalytics_email_accountsB
Get email account health and deliverability stats.
Returns:
Email account analytics including deliverability scores
Inputs: no named parameters. Returns: result
analytics_sequencesC
Get analytics for email sequences.
Args:
sequence_ids: Optional list of sequence IDs to get stats for
Returns:
Sequence performance analytics
Inputs: sequence_ids. Returns: result
contacts_searchA
Search contacts in your Apollo CRM/database.
Unlike people_search which searches Apollo's global database, this searches
contacts you've already added to your Apollo account.
Args:
q_keywords: Search keywords
contact_stage_ids: Filter by contact stage IDs
owner_id: Filter by owner user ID
emailer_campaign_ids: Filter by sequence IDs
page: Page number
per_page: Results per page
Returns:
List of contacts from your Apollo database
Inputs: q_keywords, contact_stage_ids, owner_id, emailer_campaign_ids, +2 more. Returns: result
deal_createB
Create a new deal/opportunity.
Args:
name: Deal name
account_id: Account/company ID
amount: Deal value
stage_id: Pipeline stage ID
owner_id: Owner user ID
Returns:
Created deal details
Inputs: name (required), account_id (required), amount, stage_id, +1 more. Returns: result
deals_listC
List deals/opportunities in your Apollo pipeline.
Args:
page: Page number
per_page: Results per page
stage_id: Filter by pipeline stage ID
Returns:
List of deals
Inputs: page, per_page, stage_id. Returns: result
email_previewA
Preview an email with variable substitution.
Test how your email will look with real contact data.
Args:
subject: Email subject (can include {{variables}})
body_html: Email body HTML (can include {{variables}})
contact_id: Optional contact ID to preview with real data
Returns:
Rendered email preview
Inputs: subject (required), body_html (required), contact_id. Returns: result
email_sendA
Send a one-off email to a contact.
Args:
to_email: Recipient email address
subject: Email subject
body_html: Email body HTML
contact_id: Optional contact ID to link email to
Returns:
Confirmation of email sent
Inputs: to_email (required), subject (required), body_html (required), contact_id. Returns: result
get_account_stagesB
Get available account/company stages.
Returns:
List of account stages
Inputs: no named parameters. Returns: result
get_available_fieldsB
Get all available fields/variables for email personalization.
Returns:
List of available variables that can be used in emails
Inputs: no named parameters. Returns: result
get_contact_stagesB
Get available contact stages for pipeline management.
Returns:
List of contact stages
Inputs: no named parameters. Returns: result
get_email_schedulesB
Get available email sending schedules.
Returns:
List of sending schedules with their configurations
Inputs: no named parameters. Returns: result
list_add_contactsC
Add contacts to a list.
Args:
list_id: List ID
contact_ids: Contact IDs to add
Returns:
Confirmation
Inputs: list_id (required), contact_ids (required). Returns: result
list_createB
Create a new list.
Args:
name: List name
modality: List type - "contacts" (default), "people", or "static"
Returns:
Created list details
Inputs: name (required), modality. Returns: result
lists_getC
Get all saved lists in Apollo.
Args:
page: Page number
per_page: Results per page
Returns:
List of saved lists
Inputs: page, per_page. Returns: result
organization_enrichA
Enrich an organization's profile by domain.
Get comprehensive company data including firmographics, technographics,
funding info, and more.
Args:
domain: Company domain (e.g., "stripe.com")
Returns:
Enriched organization profile
Example:
organization_enrich(domain="openai.com")
Inputs: domain (required). Returns: result
organization_job_postingsB
Get current job postings for an organization.
Useful for identifying growth signals and finding the right contacts.
Args:
organization_id: Apollo organization ID
Returns:
List of current job postings
Inputs: organization_id (required). Returns: result
organization_searchA
Search for organizations/companies in Apollo's database.
Args:
q_keywords: Keywords to search (company name, description)
organization_domains: Specific domains to find
organization_locations: HQ locations (e.g., ["California, US"])
organization_num_employees_ranges: Size ranges (e.g., ["1,10", "51,200"])
organization_industry_tag_ids: Industry filter IDs
revenue_range: Revenue filter (e.g., {"min": 1000000, "max": 10000000})
page: Page number
per_page: Results per page (max 100)
Returns:
List of matching organizations with company details
Example:
Find SaaS companies in California with 50-200 employees:
organization_search(
q_keywords="SaaS software",
organization_locations=["California, US"],
organization_num_employees_ranges=["51,200"]
)
Inputs: q_keywords, organization_domains, organization_locations, organization_num_employees_ranges, +4 more. Returns: result
people_enrichA
Enrich a person's profile with additional data from Apollo.
Provide at least one identifier (email, LinkedIn URL, or name + company).
Apollo will return comprehensive profile data including contact info,
work history, and social profiles.
Args:
email: Person's email address (best identifier)
first_name: Person's first name
last_name: Person's last name
organization_name: Current company name
domain: Company domain (e.g., "google.com")
linkedin_url: LinkedIn profile URL
Returns:
Enriched person profile with all available data
Example:
Enrich by email:
people_enrich(email="john.smith@company.com")
Enrich by name + company:
people_enrich(first_name="John", last_name="Smith", organization_name="Acme Corp")
Inputs: email, first_name, last_name, organization_name, +2 more. Returns: result
people_searchA
Search for people/contacts in Apollo's database.
This is Apollo's core prospecting tool - use it to find leads matching specific criteria.
Args:
q_keywords: Keywords to search for (e.g., "sales director")
person_titles: Job titles to filter by (e.g., ["CEO", "CTO", "VP Sales"])
person_seniorities: Seniority levels (e.g., ["c_suite", "vp", "director", "manager"])
organization_domains: Company domains to search (e.g., ["google.com", "meta.com"])
organization_locations: Company HQ locations (e.g., ["California, US", "New York, US"])
organization_num_employees_ranges: Employee count ranges (e.g., ["1,10", "11,50", "51,200"])
person_locations: Where person is located (e.g., ["San Francisco, CA"])
contact_email_status: Email verification status (e.g., ["verified", "likely_to_engage"])
page: Page number (default 1)
per_page: Results per page (default 25, max 100)
Returns:
List of matching people with contact information
Example:
Search for VPs of Sales at tech companies in California:
people_search(
person_titles=["VP Sales", "Vice President of Sales"],
organization_locations=["California, US"],
organization_num_employees_ranges=["51,200", "201,500"]
)
Inputs: q_keywords, person_titles, person_seniorities, organization_domains, +6 more. Returns: result
sequence_activateB
Activate or deactivate a sequence.
Args:
sequence_id: The sequence ID
active: True to activate, False to deactivate
Returns:
Updated sequence status
Inputs: sequence_id (required), active. Returns: result
sequence_add_contactsB
Add contacts to an email sequence.
Args:
sequence_id: The sequence ID to add contacts to
contact_ids: List of contact IDs to add
email_account_id: Optional email account to send from
Returns:
Confirmation of contacts added
Inputs: sequence_id (required), contact_ids (required), email_account_id. Returns: result
sequence_createA
Create a new email sequence with steps.
This is a powerful tool for creating automated outreach campaigns.
Args:
name: Sequence name
steps: List of step configurations. Each step should have:
- type: "auto_email", "manual_email", "phone_call", "action_item",
"linkedin_connection", "linkedin_message", "linkedin_view", "linkedin_interact"
- wait_time: Time to wait before this step (integer)
- wait_mode: "minute", "hour", or "day"
- For email steps, include emailer_touches with:
- type: "new_thread" or "reply"
- subject: Email subject (supports {{variables}})
- body_html: Email body HTML (supports {{variables}})
schedule_id: Optional sending schedule ID
active: Whether to activate immediately
Returns:
Created sequence details
Example:
sequence_create(
name="New Outreach Campaign",
steps=[
{
"type": "auto_email",
"wait_time": 0,
"wait_mode": "minute",
"emailer_touches": [{
"type": "new_thread",
"subject": "Quick question about {{company}}",
"body_html": "<p>Hi {{first_name}},</p><p>I noticed {{company}} is growing...</p>"
}]
},
{
"type": "auto_email",
"wait_time": 3,
"wait_mode": "day",
"emailer_touches": [{
"type": "reply",
"subject": "Re: Quick question about {{company}}",
"body_html": "<p>Following up on my last email...</p>"
}]
}
]
)
Available variables: {{first_name}}, {{last_name}}, {{company}}, {{title}},
{{email}}, {{phone}}, {{city}}, {{state}}, {{country}}
Inputs: name (required), steps (required), schedule_id, active. Returns: result
sequence_getB
Get detailed information about a specific sequence.
Args:
sequence_id: The sequence ID
Returns:
Sequence details including steps and stats
Inputs: sequence_id (required). Returns: result
sequences_listB
List all email sequences in your Apollo account.
Args:
page: Page number
per_page: Results per page
sort_by: Sort field (lastUsedAt, name, created_at)
Returns:
List of sequences with stats
Inputs: page, per_page, sort_by. Returns: result
task_createB
Create a new task.
Args:
contact_id: Contact ID to associate task with
task_type: Type of task (action_item, call, email, linkedin)
note: Task notes/description
due_at: Due date (ISO format)
priority: Priority level (low, medium, high)
Returns:
Created task details
Inputs: contact_id (required), task_type, note, due_at, +1 more. Returns: result
tasks_listC
List tasks in your Apollo account.
Args:
page: Page number
per_page: Results per page
status: Filter by status (pending, completed)
Returns:
List of tasks
Inputs: page, per_page, status. Returns: result
workflow_activateA
Activate or deactivate a workflow.
Note: Activation may require the workflow to have actions configured.
If activation fails, configure actions via Apollo UI first.
Args:
workflow_id: The workflow ID
active: True to activate, False to deactivate
Returns:
Updated workflow status
Inputs: workflow_id (required), active. Returns: result
workflow_createA
Create a new workflow automation.
Workflows trigger actions based on events or schedules.
Args:
name: Workflow name
trigger_type: "event" or "schedule" (default: "event")
model_type: "Contact", "Account", or "Opportunity" (default: "Contact")
trigger_events: List of trigger events (for event-based workflows):
- "contact_saved_or_created" - When a contact is saved/created
- "contact_updated" - When contact fields change
- "contact_added_to_list" - When added to a list
- "contact_added_to_sequence" - When added to a sequence
- "contact_finished_sequence" - When sequence completes
- "contact_changed_jobs" - When job change detected
- "call_logged" - When a call is logged
actions: List of actions to perform. Each action has:
- type: "add_to_sequence", "add_to_list", "update_field",
"create_task", "send_webhook", "remove_from_sequence"
- config: Action-specific configuration
enrollment_filters: Filters to determine which contacts qualify
active: Whether to activate immediately
first_run_on: Date for first run (ISO format, e.g., "2026-01-08").
Required for schedule-based workflows.
Returns:
Created workflow details
Example:
workflow_create(
name="New Lead Nurture",
trigger_type="event",
trigger_events=["contact_saved_or_created"],
actions=[
{"type": "add_to_sequence", "config": {"sequence_id": "abc123"}}
]
)
Inputs: name (required), trigger_type, model_type, trigger_events, +4 more. Returns: result
workflow_create_from_templateC
Create a new workflow from a template.
Args:
template_id: The template ID to use
name: Optional custom name for the workflow
Returns:
Created workflow details
Inputs: template_id (required), name. Returns: result
workflow_deleteC
Delete a workflow.
Args:
workflow_id: The workflow ID to delete
Returns:
Confirmation of deletion
Inputs: workflow_id (required). Returns: result
workflow_getA
Get detailed information about a specific workflow.
Args:
workflow_id: The workflow ID
Returns:
Workflow details including triggers, actions, and enrollment criteria
Inputs: workflow_id (required). Returns: result
workflows_listB
List all workflows in your Apollo account.
Workflows automate actions based on triggers (events or schedules).
Args:
page: Page number
per_page: Results per page
active_only: Only show active workflows
Returns:
List of workflows with their status and configuration
Inputs: page, per_page, active_only. Returns: result
workflow_templates_listB
List available workflow templates.
Templates provide pre-built workflows for common automation scenarios.
Args:
page: Page number
per_page: Results per page
Returns:
List of workflow templates
Inputs: page, per_page. Returns: result
workflow_updateB
Update an existing workflow.
Args:
workflow_id: The workflow ID to update
name: New workflow name
trigger_events: Updated trigger events
actions: Updated actions
enrollment_filters: Updated enrollment filters
active: Set active/inactive status
Returns:
Updated workflow details
Inputs: workflow_id (required), name, trigger_events, actions, +2 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 34 tools
Most tools have distinct purposes, but there is some overlap between 'contacts_search' and 'people_search' (both search contacts, though one targets the user's database and the other Apollo's global database), and between 'sequence_activate' and 'workflow_activate' (both activate/deactivate automation). Descriptions help clarify, but agents might occasionally confuse these pairs.
Tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., 'analytics_email_accounts', 'contacts_search', 'deal_create'). The naming is predictable across all 34 tools, making it easy for agents to understand and navigate the set.
With 34 tools, the count is borderline high for a CRM/outreach server, as it may feel heavy and complex for agents to manage. While it covers many aspects (analytics, contacts, deals, emails, sequences, tasks, workflows), some consolidation or scoping might improve usability without sacrificing functionality.
The tool set provides comprehensive coverage for Apollo's domain, including CRUD operations for contacts, deals, lists, sequences, tasks, and workflows, plus enrichment, search, analytics, and email capabilities. There are no obvious gaps; agents can perform end-to-end workflows from prospecting to automation.
Maintenance
Related MCP Connectors
Prospect, enrich leads, and manage outreach sequences with Apollo.io.
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.
Find prospects, enrich contacts, track buying signals and run email and LinkedIn outreach.
Apollo.io MCP — company and people data via api.apollo.io, the caller's OWN Apollo account (fleet…
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Apollo.io API for sales and marketing activities. Provides tools to search for companies and contacts, enrich person and organization data, and manage accounts with comprehensive lead generation capabilities.11MIT
- AlicenseBqualityDmaintenanceIntegrates Apollo.io's B2B sales platform with Claude AI, enabling prospect search, contact enrichment, email sequence management, list analytics, and sales intelligence operations through natural conversation.191MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the Apollo.io API to search global databases and enrich company and person data. It facilitates managing contacts and accounts, retrieving tech stacks, and finding job postings through natural language.1MIT
- FlicenseBqualityDmaintenanceExposes Apollo.io API functionalities as MCP tools for people and organization enrichment, search, and job postings. Enables natural language interaction with Apollo.io data.516-