Apollo.io MCP Server

The official Apollo.io Model Context Protocol server for prospecting, lead enrichment, sales intelligence, and outreach workflows.

Provider: Official, first-party server built and maintained by Apollo.io.

Bring Apollo.io prospecting, enrichment, and outreach directly into your favorite MCP-compatible AI application — GitHub Copilot, Visual Studio Code, Cursor, Claude Code, Claude Desktop, and Claude Cowork.

• Apollo.io: https://www.apollo.io/
• Model Context Protocol: https://modelcontextprotocol.io/
• License: MIT

Table of Contents

• Overview
• Key Capabilities
• Prerequisites
• Install in Visual Studio Code and GitHub Copilot
• Install in Cursor
• Install in Claude Code
• Install in Claude Desktop or Claude Cowork
• Generic MCP Client Configuration
• Authentication and Authorization
• Usage Examples
• Available Tools and Capabilities
• Model Recommendations
• Safety and Responsible Usage
• Privacy and Data Handling
• Troubleshooting
• Official MCP Registry
• Development and Contribution
• Versioning and Releases
• Security
• Support
• Credits
• License

Overview

The Apollo.io MCP server exposes Apollo.io's go-to-market data and workflows through the Model Context Protocol, so MCP-compatible AI applications can prospect for people and companies, enrich contacts, query sales analytics, and load leads into outreach sequences using natural language.

• Hosted and maintained by Apollo.io. The server runs remotely — there is nothing to build, host, or run locally.

• Transport: Streamable HTTP.

• Endpoint:

  text

  https://mcp.apollo.io/mcp
  

• Authentication: Handled through Apollo.io OAuth. You sign in with your Apollo.io account and authorize access from your MCP client; the server then acts with your Apollo.io permissions. See Authentication and Authorization.

This repository also ships an optional Apollo plugin for Claude Code and Cowork that bundles ready-made workflow skills (/apollo:* commands) on top of the same MCP server.

Key Capabilities

The following capabilities are confirmed by the server tools and skills in this repository:

• People prospecting — search Apollo's people database by title, seniority, location, and company attributes.
• Company prospecting — search organizations by industry, size, location, and keywords.
• Contact and account enrichment — match and enrich people and organizations, individually or in bulk.
• Outreach sequence workflows — find sequences, and add or remove/stop contacts in a sequence.
• Sales analytics — query email, call, meeting, task, opportunity, sequence, and conversation-intelligence metrics and return formatted breakdowns.
• Contact management — create Apollo contacts as part of enrichment and sequence-loading workflows.

The remote server may expose additional tools beyond those exercised by the bundled skills. The list above reflects what is confirmed in this repository. See Available Tools and Capabilities.

Prerequisites

• An Apollo.io account. Sign in at https://www.apollo.io/.

• Apollo.io permissions and credits. Actions run with your account's permissions, and some actions consume Apollo credits (for example, enrichment). See Safety and Responsible Usage. For plan, credit, and permission details, see the Apollo documentation.

• An MCP-compatible client that supports the Streamable HTTP transport, such as:

  • GitHub Copilot in Visual Studio Code
  • Cursor
  • Claude Code
  • Claude Desktop / Claude Cowork
  • Other MCP clients (see Generic MCP Client Configuration)

• No local runtime required. The server is remote and hosted by Apollo.io — you do not need Node.js, Docker, or a local installation to use it. (The optional Claude Code / Cowork plugin installs workflow skills locally through your client's plugin system, but the MCP server itself remains remote.)

Install in Visual Studio Code and GitHub Copilot

The Apollo.io MCP server is published in the official Model Context Protocol Registry, but it is not yet discoverable in the curated GitHub MCP Registry or the VS Code MCP gallery. Until then, add it manually with the configuration below.

Option A — workspace configuration file

Create a .vscode/mcp.json file in your workspace:

{
  "servers": {
    "apollo": {
      "type": "http",
      "url": "https://mcp.apollo.io/mcp"
    }
  }
}

Option B — command palette

1. Open the Command Palette (Cmd/Ctrl + Shift + P).
2. Run MCP: Add Server.
3. Choose the HTTP (Streamable HTTP) server type when prompted.
4. Enter the URL https://mcp.apollo.io/mcp and name the server apollo.

Expected authentication and first run

1. Add the MCP server using either option above.
2. Start or enable the apollo server.
3. Complete Apollo.io authentication in the browser window that opens.
4. Approve the requested access for your Apollo.io workspace.
5. Open Copilot Chat in Agent mode.
6. Confirm that the Apollo tools are listed and available to the agent.

For the current terminology and behavior, see the VS Code documentation on MCP servers: https://code.visualstudio.com/docs/copilot/chat/mcp-servers.

Install in Cursor

Add the remote Streamable HTTP endpoint to your Cursor MCP configuration (for example, ~/.cursor/mcp.json, or the project-level .cursor/mcp.json):

{
  "mcpServers": {
    "apollo": {
      "type": "http",
      "url": "https://mcp.apollo.io/mcp"
    }
  }
}

Then:

1. Open Cursor settings and confirm the apollo server is listed under MCP.
2. Authenticate with your Apollo.io account when prompted.
3. Approve the requested access, then use Apollo tools from the agent.

This repository also includes a Cursor plugin manifest (.cursor-plugin/plugin.json) that references the same remote endpoint (.mcp.json), so no local package needs to run.

Install in Claude Code

You can connect the server in either of two ways.

Option A — add the remote MCP server directly

claude mcp add --transport http apollo https://mcp.apollo.io/mcp

Then run /mcp inside Claude Code, select apollo, and authenticate.

Option B — install the Apollo plugin (adds /apollo:* workflow skills)

1. Add this plugin's marketplace:

   text

   /plugin marketplace add apolloio/apollo-mcp-plugin
   

2. Install the plugin:

   text

   /plugin install apollo@apollo-plugin-marketplace
   

3. Restart Claude Code so the MCP server starts correctly.

The plugin automatically configures the Apollo MCP server — no manual config files. After installing, authenticate with /mcp and run /apollo:* commands (see Available Tools and Capabilities).

Install in Claude Desktop or Claude Cowork

Claude Desktop and Claude Cowork are separate from Claude Code (the CLI). Use the steps below for the desktop-based clients.

Cowork (one-click)

Click to install in a single step:

Install in Cowork

Then restart Cowork so the MCP server starts correctly.

Claude Desktop

Add the Apollo connector from your Claude settings, then authenticate:

1. Open Settings and connect the Apollo.io connector (Apollo appears as a remote MCP server).
2. Complete Apollo.io authentication in your browser.
3. Approve the requested access.
4. Confirm Apollo tools are available in a new chat.

Exact menu labels and navigation vary by Claude Desktop version. See Anthropic's documentation for the current steps to add a remote MCP connector.

Generic MCP Client Configuration

For any other MCP-compatible client that supports Streamable HTTP:

{
  "name": "apollo",
  "type": "streamable-http",
  "url": "https://mcp.apollo.io/mcp"
}

Exact property names vary between clients. Some clients use type: "http" (as in the VS Code and Cursor examples above) and some use type: "streamable-http". Consult your client's MCP documentation for the precise schema.

Authentication and Authorization

The Apollo MCP server uses Apollo.io OAuth. Only confirmed behavior is documented here.

• Sign-in flow. When you connect the server, your client opens an Apollo.io sign-in and authorization window. After you approve access, your client can call Apollo tools on your behalf.
• Workspace and permissions. The server acts with the authenticated user's Apollo.io permissions. You can only access data and perform actions your Apollo.io account is allowed to.
• Reconnecting. In Claude Code you can re-run /mcp, select apollo, and re-authenticate. In other clients, re-trigger authentication from the client's MCP or connector settings.
• Revoking access. Remove or disconnect the apollo server from your MCP client to stop it from acting on your behalf. To manage authorizations at the account level, use your Apollo.io account settings.

OAuth authorization-server metadata is discoverable at https://mcp.apollo.io/.well-known/oauth-authorization-server. Beyond that, this README does not assert a specific OAuth specification or profile.

Usage Examples

Natural-language prompts you can try once the server is connected:

Find software engineering leaders at B2B SaaS companies in Germany with 200–1,000 employees.

Enrich these business contacts and return their current title, company, and verified business email when available.

Show email and call performance by rep for this quarter, sorted by calls made.

Add the selected contacts to my Apollo sequence "Q1 Enterprise Outbound" — show a preview before enrolling.

If you installed the Claude Code / Cowork plugin, the same workflows are available as slash commands:

• /apollo:prospect VP of Engineering at Series B+ SaaS companies in the US, 200-1000 employees
• /apollo:enrich-lead https://www.linkedin.com/in/example
• /apollo:sequence-load add 20 VP Sales at SaaS companies to my "Q1 Outbound" sequence
• /apollo:analytics Show me team call connect rate this quarter by rep

Review before you act. For consequential actions — enrichment (credit-consuming) and adding contacts to a sequence (potentially outbound) — review the exact targets and parameters before confirming the operation.

Available Tools and Capabilities

The remote server provides the underlying Apollo tools; the tools listed below are those confirmed in this repository through the bundled workflow skills. The full, authoritative tool set is provided by the remote server and may evolve independently of this document.

Workflow skills (Claude Code / Cowork plugin)

High-value skills that chain multiple Apollo tools into complete workflows:

Underlying Apollo tools referenced by the skills

Some actions (such as enrichment) consume Apollo credits. For per-tool credit costs and the authoritative, up-to-date tool reference, see the Apollo documentation.

Model Recommendations

For clients where you can choose a model (for example, Claude Code via /model):

• Opus (best quality) — strongest reasoning and the most reliable multi-step tool orchestration. Best for prospecting workflows, ambiguous matches, multi-step chaining, and high-stakes tasks. Tradeoff: higher latency and usage cost.
• Sonnet (faster) — good for quick lookups, lightweight enrichment, and rapid iteration. Tradeoff: may need more guidance on complex multi-step workflows.

Safety and Responsible Usage

• Review prospecting results before using or exporting them.
• Follow applicable privacy, marketing, anti-spam, and data-protection laws in your jurisdiction and your recipients'.
• Confirm recipients before adding anyone to an outreach sequence. Depending on your sequence and sending configuration, enrollment may start outbound automatically. Always verify the sequence name, sending account, and enrollment volume before confirming.
• Be aware of Apollo credit consumption. Some actions (such as enrichment) consume Apollo credits, and bulk actions scale with volume. This repository's skills are designed to warn and request confirmation before credit-consuming actions. For credit costs, see the Apollo documentation.
• Avoid bulk or destructive actions without reviewing their exact scope first.
• Respect Apollo account permissions and your organization's policies.

This section is guidance, not legal advice.

Privacy and Data Handling

• Requests are sent to the Apollo-hosted MCP endpoint (https://mcp.apollo.io/mcp).
• The server interacts with Apollo data under your authenticated account and permissions.
• Avoid sending unnecessary sensitive information in prompts.

For Apollo.io's official privacy and security resources:

• Privacy Policy: https://www.apollo.io/privacy-policy
• Privacy Center: https://www.apollo.io/company/privacy-center
• Security: https://www.apollo.io/product/security
• Trust Center: https://trust.apollo.io/

Troubleshooting

Official MCP Registry

This server is published and active in the official Model Context Protocol Registry.

Publication in the official Model Context Protocol Registry is separate from the curated GitHub MCP Registry and the VS Code MCP gallery. Being active in the official registry does not automatically make the server discoverable in those curated catalogs.

Development and Contribution

This repository contains the Apollo MCP client configuration, the Claude/Cursor plugin manifests, workflow skills, and the registry metadata. The MCP server itself is hosted by Apollo.io.

Repository layout:

Validating server.json

server.json follows the MCP server schema referenced at the top of the file. Publication is automated by the CI workflow (see below), which downloads the official mcp-publisher and runs mcp-publisher publish.

There is no standalone validate command. To check server.json locally before pushing, run a dry-run publish with the official CLI:

mcp-publisher publish --dry-run

Contributions are welcome via pull requests. Please keep version metadata consistent across server.json, .claude-plugin/plugin.json, and .cursor-plugin/plugin.json.

Versioning and Releases

• The server version is declared in server.json (version: 0.1.1) and mirrored in the plugin manifests (.claude-plugin/plugin.json, .cursor-plugin/plugin.json).
• On every push to main that changes server.json, the publish-mcp.yml workflow publishes the new version to the official Model Context Protocol Registry (authenticating via GitHub OIDC).
• Keep the version in server.json and the plugin manifests aligned before publishing, so the repository and the registry stay in sync.
• Releases are driven by server.json changes on main — the repository does not cut GitHub Releases or version tags per version.

Security

Please do not report security vulnerabilities through public GitHub issues.

Report suspected vulnerabilities privately through the Apollo Trust Center. See SECURITY.md for the full disclosure process and scope.

Support

Credits

• MCP Server by Apollo.io
• Plugin specification by Anthropic

License

MIT — see LICENSE for details. Copyright (c) 2025 Apollo.io.