Apollo MCP connector
Connect Apollo to Elaichi and Claude, ChatGPT, Cursor, or any MCP client can search people and companies and enrich contacts and accounts, with every lookup running inside each person's own Apollo access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Apollo to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Apollo once
-
Open Connections, choose Add connection, and pick Apollo.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Apollo API key. One person generates a token in Apollo and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
Apollo
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Apollo MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Apollo MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Apollo MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Apollo MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Apollo to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Apollo through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Research an account before the first call
Ask for the company's size, industry, location and funding from Apollo, then the people who hold the titles you sell to. Walk in knowing who matters.
-
Sales Development
Build a prospect list from a plain description
Describe the titles, industries and regions you want and get a list of matching people from Apollo. Narrow it by company size or seniority in the next message.
-
Sales Development
Fill in a lead's email and phone
Give a name and a company and Apollo returns the work email, phone, title and LinkedIn profile. No more copying one field at a time.
-
Marketing
Find lookalike companies for a campaign
Start from a customer you already have and ask Apollo for companies with the same industry, headcount and technology. Hand the list to the team that runs the campaign.
-
Revenue Operations
Clean up a record with missing fields
Paste a company domain and get its full Apollo profile, including industry, employee count and headquarters, so the account in your CRM is complete.
-
Recruiting
Map the people at a target company
Ask Apollo who works in engineering or product at a company you are hiring from, with titles and seniority, before anyone writes an outreach message.
Try asking
- “Find VP Sales contacts at fintech companies in Austin”
- “Enrich Priya Shah at Northwind with work email and phone”
- “Which SaaS companies in London have 200 to 500 employees?”
Compare
Elaichi vs Zapier MCP vs Composio for Apollo
All three can connect Apollo to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Apollo tools | Allow or restrict single Apollo tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Apollo call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Apollo tools for your AI agents
4 tools are ready to call through Elaichi's MCP endpoint the moment you connect Apollo, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Apollo gets you
6 screens from the product, each doing one job for your Apollo account.
The agent
Ask Apollo for prospects in plain language.
Describe the titles, industries and regions you want and get live people and companies back.
- people
- companies
- contacts
- organizations
Ask Elaichi to work across your apps.
Find VP Sales contacts at fintech companies in Austin
Enrich Priya Shah at Northwind with work email and phone
Which SaaS companies in London have 200 to 500 employees?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Apollo to every client.
Claude, ChatGPT and Cursor connect to Apollo over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
4 Apollo tools, no code to write.
Search people, search companies, and enrich either one, ready the moment Apollo is connected.
- Apollo people enrichment match
- Apollo organizations enrich
- List all Apollo mixed people
- List all Apollo mixed companies
Toolboxes
Each team gets its own Apollo toolbox.
Sales, marketing and recruiting each see the Apollo lookups their work needs.
- Sales
- Sales Development
- Marketing
- Revenue Operations
Shared connections
Teammates use Apollo without seeing the key.
One person connects Apollo, shares it with a team, and nobody else handles a credential.
- Sales EMEA
- Sales North America
- Outbound
- Marketing
Audit log
Every Apollo lookup names who ran it.
When, who, what happened and which person or company, in an append-only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts real prospecting work.
New Apollo people are fetched, grouped, drafted into a digest, approved by a person, then posted.
Apollo digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch people
Apollo
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Apollo
Queued
Collections and dashboards
Apollo numbers, computed without a model.
Searches, enrichments, people matched and companies enriched, by team, refreshed on a schedule.
Apollo health
Refreshed 4 minutes ago · every 15 minutes · from the people collection
People
1,284 ↓ 12%
Companies
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
People created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales North America 27%
Outbound 21%
Marketing 18%
FAQ
Frequently asked questions
How do I connect Apollo to Claude?
Connect Apollo in Elaichi first: Apollo signs in with an API key, which you paste in once, and there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi as yourself and Apollo is available in Claude from that point on.
Does Apollo work with ChatGPT and Cursor as well as Claude?
Yes. Apollo is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is added to Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent. There is nothing separate to set up for each client.
What can an AI agent actually do with my Apollo data?
With Apollo connected, an AI agent can search for people by title, seniority, industry and location, search for companies by size, industry and technology, and enrich a single person or company with email, phone, headcount and other profile fields. Short concrete asks work best, such as a name and a company, or a title and a region. This connector looks things up and fills in details; it does not change anything in Apollo.
Does connecting Apollo give the AI everything in my Apollo account?
No. Every Apollo request runs as the person who signed in to Elaichi, so the agent can see only what that person's own Apollo account and credits allow. Elaichi can narrow that further by restricting actions for a team, and it can never widen access beyond what the person already has in Apollo.
Can I stop an agent from deleting or changing things in Apollo?
The Apollo connector only searches and enriches people and companies, so it has no way to delete or edit records in Apollo. Restrictions still work per action: if you restrict enrichment for a team, that action is removed from what their AI client can reach and cannot be called, whatever the prompt says.
What happens to an Apollo connection when someone leaves?
Offboarding a person in Elaichi ends their access to Apollo through every client at once. A shared Apollo connection keeps working for everyone else on the team. If you want Apollo gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the Apollo MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Apollo is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Apollo?
Yes. Both let Claude, ChatGPT or Cursor use Apollo. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Apollo call.
How is Elaichi different from Composio for Apollo?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Apollo: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Apollo in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.