
Apollo.io
io.github.apolloio由 GitHub 账号 apolloio 发布v0.1.1更新于 Oct 24, 2026
Prospect, enrich leads, and manage outreach sequences with Apollo.io.
概览
Apollo.io 官方远程 MCP 服务器,让助手挖掘人物与公司、丰富线索、管理外联序列并查询销售分析数据。
- 可以做什么
- 按职位、资历、地点、行业、规模和关键词搜索 Apollo 的人物与公司数据库,并对单个或批量联系人和组织进行匹配与丰富。创建 Apollo 联系人,并按名称查找外联序列。将联系人加入序列,或从序列中移除和停止联系人,并列出已连接的邮件发件账户。查询邮件、通话、会议、任务、商机和序列等销售分析指标与分类明细。
- 适用场景
- 适合已使用 Apollo.io 的销售和市场团队,希望在聊天客户端中用自然语言完成客户挖掘、线索丰富、序列导入和业绩报表。
- 运行要求
- 由 Apollo.io 托管的远程 Streamable HTTP 端点,无需本地运行时、Node.js 或 Docker。需要具备相应权限和额度的 Apollo.io 账户,并通过 MCP 客户端完成 OAuth 登录与授权。客户端需支持 Streamable HTTP,且端点需能通过企业代理或防火墙访问。
安装
在 SourceWeft 中
- 打开 控制台中的 Apollo.io,将其添加到工作区。
- 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.apolloio%2Fapollo-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。
{
"mcpServers": {
"apollo-io": {
"type": "http",
"url": "https://mcp.apollo.io/mcp"
}
}
}README
Apollo.io MCP Server
The official Apollo.io Model Context Protocol server for prospecting, lead enrichment, sales intelligence, and outreach workflows.
[License: MIT] [MCP Registry] [Version]
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:
-
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:
Option B — command palette
- Open the Command Palette (
Cmd/Ctrl + Shift + P). - Run MCP: Add Server.
- Choose the HTTP (Streamable HTTP) server type when prompted.
- Enter the URL
https://mcp.apollo.io/mcpand name the serverapollo.
Expected authentication and first run
- Add the MCP server using either option above.
- Start or enable the
apolloserver. - Complete Apollo.io authentication in the browser window that opens.
- Approve the requested access for your Apollo.io workspace.
- Open Copilot Chat in Agent mode.
- 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):
Then:
- Open Cursor settings and confirm the
apolloserver is listed under MCP. - Authenticate with your Apollo.io account when prompted.
- 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
Then run /mcp inside Claude Code, select apollo, and authenticate.
Option B — install the Apollo plugin (adds /apollo:* workflow skills)
-
Add this plugin's marketplace:
-
Install the plugin:
-
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:
Then restart Cowork so the MCP server starts correctly.
Claude Desktop
Add the Apollo connector from your Claude settings, then authenticate:
- Open Settings and connect the Apollo.io connector (Apollo appears as a remote MCP server).
- Complete Apollo.io authentication in your browser.
- Approve the requested access.
- 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:
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.
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
apolloserver 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:
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:
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
mainthat changesserver.json, thepublish-mcp.ymlworkflow publishes the new version to the official Model Context Protocol Registry (authenticating via GitHub OIDC). - Keep the version in
server.jsonand the plugin manifests aligned before publishing, so the repository and the registry stay in sync. - Releases are driven by
server.jsonchanges onmain— 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
License
MIT — see LICENSE for details. Copyright (c) 2025 Apollo.io.
来源:README.md,提交 bd0513c
工具
0版本历史
1- v0.1.1最新Sep 16, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分