MCP100 verdict
Not currently recommended. Shortlist — editorially admitted, not a Recommended endorsement.
MCP100 Assessment
Editorial verdict
Reviewed October 19, 2026
Task Fit
Mapped
Specialized workflows
Trust
Status warning
Show mandatory vendor restriction and avoid recommending clients with training enabled
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals unavailable
No independently comparable adoption metric is currently stored.
Evidence scope
30 shared-repository stars · not MCP-specific
No MCP-specific package metric is stored
Repository identity: apolloio/apollo-mcp-plugin
Stars observed October 20, 2026 · Downloads observed October 20, 2026
Official Apollo repository contains remote MCP configuration, registry metadata, plugins, and workflow skills; the server itself is hosted by Apollo.io. Stars are distribution/plugin evidence, not hosted server implementation adoption.
Apollo.io's current MCP server is hosted; its repository distributes remote configuration/plugins/skills and no exact server package is published.
Publisher activity observed October 19, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed October 19, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
Complete client-specific setup, verification and removal are not documented in this reviewed source.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-10-19
Type-appropriate, source-backed setup for this mcp server profile.
Loading optional publisher installation details…
{"url":"https://mcp.apollo.io/mcp"}Capability
Apollo.io MCP is a Apollo.io MCP integration for apollo prospecting, enrichment and account research. Use for teams already authorized to access Apollo. Contact and sales data access/exports are governed by account permissions and contractual restrictions.
Remote server inventory may evolve independently of bundled skills; do not count plugin skills as MCP tools
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
https://mcp.apollo.io/mcp
Reviewed access
Related reviewed MCPs
Connect compatible AI clients to Contentful's documented MCP capabilities.
Choose this instead if
Choose Contentful MCP Server instead if connect compatible AI clients to Contentful's documented MCP capabilities.
Recommended after reviewed 2026-09-25 admission dossier: current_patched_first_party_server_all_selected_gates_pass.
Google Search Console MCP Server for SEOs
Choose this instead if
Choose Google Search Console MCP Server for SEOs instead if sEO analysis across Search Console properties, queries, pages, indexing status, and sitemaps.
Recommended for teams that want an AI assistant to inspect Search Console performance and indexing data through a deliberately scoped Google account.
Let AI clients inspect and automate web browsers with Playwright.
Choose this instead if
Choose Playwright MCP instead if inspecting and testing web interfaces through accessibility snapshots.
Let AI clients inspect and automate web browsers with Playwright.
Apollo.io is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
From the publisher README
Original client setup and configuration retained from the publisher documentation.
Publisher-documented clients
These names appear in the publisher's installation documentation. MCP100-verified configurations are shown separately above when available.
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.
Create a .vscode/mcp.json file in your workspace:
{
"servers": {
"apollo": {
"type": "http",
"url": "https://mcp.apollo.io/mcp"
}
}
}
Cmd/Ctrl + Shift + P).https://mcp.apollo.io/mcp and name the server apollo.apollo server.For the current terminology and behavior, see the VS Code documentation on MCP servers: https://code.visualstudio.com/docs/copilot/chat/mcp-servers.
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:
apollo server is listed under MCP.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.
You can connect the server in either of two ways.
claude mcp add --transport http apollo https://mcp.apollo.io/mcp
Then run /mcp inside Claude Code, select apollo, and authenticate.
/apollo:* workflow skills)Add this plugin's marketplace:
/plugin marketplace add apolloio/apollo-mcp-plugin
Install the plugin:
/plugin install apollo@apollo-plugin-marketplace
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).
Claude Desktop and Claude Cowork are separate from Claude Code (the CLI). Use the steps below for the desktop-based clients.
Click to install in a single step:
Then restart Cowork so the MCP server starts correctly.
Add the Apollo connector from your Claude settings, then authenticate:
Exact menu labels and navigation vary by Claude Desktop version. See Anthropic's documentation for the current steps to add a remote MCP connector.
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
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.
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:
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.
The following capabilities are confirmed by the server tools and skills in this repository:
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.
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:
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.)
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 usetype: "streamable-http". Consult your client's MCP documentation for the precise schema.
The Apollo MCP server uses Apollo.io OAuth. Only confirmed behavior is documented here.
/mcp, select apollo, and re-authenticate. In other clients, re-trigger authentication from the client's MCP or connector settings.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.
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 repReview 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.
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.
High-value skills that chain multiple Apollo tools into complete workflows:
| Skill | What it does |
|---|---|
/apollo:enrich-lead | Drop a name, LinkedIn URL, or email and get a full contact card with company context and next actions. |
/apollo:prospect | Describe your ICP in plain English and get a ranked table of enriched decision-makers. |
/apollo:sequence-load | Find leads, enrich them, dedupe, and bulk-add them to an Apollo sequence with a preview before enrollment. |
/apollo:analytics | Ask any sales performance question and get formatted tables from real Apollo analytics data. |
| Tool | Description | Data effect | Outreach / external action |
|---|---|---|---|
apollo_mixed_people_api_search | Search Apollo's people database by title, seniority, location, and company filters. | Reads | No |
apollo_mixed_companies_search | Search Apollo's organization database by industry, size, location, and keywords. | Reads | No |
apollo_people_match | Match and enrich a single person from available identifiers. | Reads / enriches | No |
apollo_people_bulk_match | Match and enrich multiple people in one call. | Reads / enriches | No |
apollo_organizations_enrich | Enrich a single organization. | Reads / enriches | No |
apollo_organizations_bulk_enrich | Enrich multiple organizations in one call. | Reads / enriches | No |
apollo_contacts_create | Create a contact in the Apollo workspace. | Changes Apollo data | No |
apollo_emailer_campaigns_search | Find outreach sequences by name. | Reads | No |
apollo_emailer_campaigns_add_contact_ids | Add contacts to an outreach sequence. | Changes Apollo data | Yes — may start outbound depending on sequence settings. |
apollo_emailer_campaigns_remove_or_stop_contact_ids | Remove or stop contacts in an outreach sequence. | Changes Apollo data | Affects active outreach |
apollo_email_accounts_index | List connected email/sending accounts. | Reads | No |
apollo_analytics_sync_report | Retrieve sales analytics metrics and breakdowns. | Reads | No |
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.
For clients where you can choose a model (for example, Claude Code via /model):
This section is guidance, not legal advice.
https://mcp.apollo.io/mcp).For Apollo.io's official privacy and security resources:
| Symptom | What to check |
|---|---|
| Authentication window does not open | Ensure pop-ups are allowed; re-trigger authentication from your client's MCP/connector settings. |
| Authentication session expired | Re-authenticate (in Claude Code, run /mcp → apollo → authenticate). |
| Server is not starting | Restart the client after adding/installing; confirm the endpoint URL is exactly https://mcp.apollo.io/mcp. |
| Tools do not appear | Confirm the server is enabled and authenticated, and (for Copilot) that chat is in Agent mode. |
| "Permission denied" on an action | Your Apollo.io account may lack the required permission for that action. |
| Credits unavailable | Enrichment and some actions require Apollo credits; confirm your workspace has credits available. |
| Client does not support Streamable HTTP | Use a client that supports the Streamable HTTP transport, or the generic config in Generic MCP Client Configuration. |
| Invalid JSON in config | Validate your mcp.json / client config with a JSON linter — a trailing comma or missing brace will prevent the server from loading. |
| Corporate proxy or firewall blocks the endpoint | Ensure https://mcp.apollo.io is reachable through your network/proxy allowlist. |
This server is published and active in the official Model Context Protocol Registry.
| Field | Value |
|---|---|
| Registry name | io.github.apolloio/apollo-mcp |
| Version | 0.1.1 |
| Transport | Streamable HTTP |
| Endpoint | https://mcp.apollo.io/mcp |
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.
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:
| Path | Purpose |
|---|---|
.mcp.json | Remote MCP server definition (apollo → https://mcp.apollo.io/mcp). |
server.json | Official MCP Registry metadata (name, version, transport, endpoint). |
.claude-plugin/ | Claude Code / Cowork plugin and marketplace manifests. |
.cursor-plugin/ | Cursor plugin manifest. |
glama.json | Glama MCP directory metadata. |
skills/ | Workflow skills: prospect, enrich-lead, sequence-load, analytics. |
.github/workflows/publish-mcp.yml | CI that publishes server.json to the MCP Registry. |
server.jsonserver.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.
server.json (version: 0.1.1) and mirrored in the plugin manifests (.claude-plugin/plugin.json, .cursor-plugin/plugin.json).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).server.json and the plugin manifests aligned before publishing, so the repository and the registry stay in sync.server.json changes on main — the repository does not cut GitHub Releases or version tags per version.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.
| Need | Where to go |
|---|---|
| Apollo product support (data, credits, account, billing) | Apollo Knowledge Base or contact Apollo Support |
| Apollo product documentation | docs.apollo.io |
| MCP integration bugs (this repository) | Open a GitHub issue on apolloio/apollo-mcp-plugin |
| Feature requests | Open a GitHub issue on apolloio/apollo-mcp-plugin |
| Security vulnerabilities | Do not open a public issue — see Security |
MIT — see LICENSE for details. Copyright (c) 2025 Apollo.io.