RocketReach MCP connector
The RocketReach connector brings people search, company search, contact lookups, bulk enrichment and email verification into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with every lookup governed and logged by Elaichi.
- Connects with an API key
- Free 14-day trial
- No credit card
Find the VP of sales at Snowflake and get a verified email.
Working in RocketReach with Elaichi
-
List all RocketReach search people
-
List all RocketReach universal search people
-
List all RocketReach search companies
How to connect RocketReach to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
RocketReach 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.
RocketReach 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.
RocketReach 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. The plugin directory lives at chatgpt.com/plugins.
RocketReach 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.
RocketReach MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect RocketReach 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.
What teams do with RocketReach through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in RocketReach is logged.
-
Sales
Find the right person before the first call
Ask for the head of procurement at a target account and get back a name, a verified work email and a direct dial from RocketReach. The record is ready before you pick up the phone.
-
Sales development
Verify emails before a sequence goes out
Run a RocketReach email verification on the addresses in tomorrow's outreach so bounces stay low and the domain stays healthy.
-
Marketing
Build a targeted list for the next campaign
Search RocketReach for people by title, industry and location, then look up their contact details in bulk and hand the list to the campaign owner.
-
Recruiting
Reach passive candidates at their work email
Search for engineers with the skills and employers you want, then look up how to reach them without leaving the conversation.
-
Partnerships
Size up a company before reaching out
Look up a company in RocketReach to see its headcount, industry, location and who leads the teams you want to partner with.
-
Revenue operations
Enrich a batch of leads in one go
Hand over a list of names and companies, start a bulk lookup in RocketReach, and check its status until the emails and phone numbers are back.
Try asking
- “Find the VP of sales at Snowflake and get a verified email.”
- “Which fintech companies in Austin have more than 500 employees?”
- “Verify these five email addresses before the sequence goes out.”
What connecting RocketReach gets you
6 screens from Elaichi, each doing one job for your RocketReach account.
Ask Elaichi to work across your apps.
Find the VP of sales at Snowflake and get a verified email.
Which fintech companies in Austin have more than 500 employees?
Verify these five email addresses before the sequence goes out.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask for a prospect's email in plain language.
Elaichi's agent answers from live RocketReach people and company records.
Copy the endpoint
AI apps
Use RocketReach from Claude, ChatGPT or Cursor.
One governed endpoint, signed in over OAuth, no SDK and no shared API key.
Tool catalog
All 16 RocketReach tools, no custom code.
People search, company lookup, bulk enrichment and email verification, ready the moment you connect.
Toolboxes
Each team gets its own RocketReach toolbox.
Sales, Recruiting and Marketing each work from the toolbox scoped to them.
Shared connections
Share one RocketReach account, never the key.
Teammates search people and look up contacts through a connection without seeing the credential.
Audit log
Every RocketReach lookup is logged with a name.
When, who, what happened, type and resource, for every call, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
RocketReach digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch people
RocketReach
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 Jake Morgan
Approve Deny -
Post the digest
RocketReach
Queued
Workflows
A schedule runs RocketReach enrichment end to end.
New lookups are fetched, grouped by company, drafted into a digest, approved, then returned to RocketReach.
RocketReach 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 US 27%
Sales development 21%
Marketing 18%
Collections and dashboards
RocketReach usage reported without anyone asking.
Lookups, verifications and credits counted straight from RocketReach over 14 days, split by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for RocketReach
All three can connect RocketReach 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 RocketReach tools | Allow or restrict single RocketReach 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 RocketReach 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 | Free for one person; $15 per user per month on Gold. | 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.
RocketReach tools for your AI agents
16 tools are ready to call through Elaichi's MCP endpoint the moment you connect RocketReach, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect RocketReach to Claude?
Connect RocketReach in Elaichi by pasting your RocketReach API key when asked. 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 with your Elaichi account and RocketReach is ready to use in Claude.
Does RocketReach work with ChatGPT and Cursor as well as Claude?
Yes. Once RocketReach is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect RocketReach once and every client picks it up.
What can an AI agent actually do with my RocketReach data?
It can search RocketReach for people by title, company, location or skills, search for companies, and look up a person's work email and phone, one at a time or in a batch. It can check whether a bulk lookup has finished, verify an email address before you send to it, and tell you how many lookup credits your RocketReach account has left. Short, concrete asks such as "find the VP of sales at Acme" work better than long sentences.
Does connecting RocketReach give the AI my whole account and all its credits?
The agent can only do what the connected RocketReach API key allows, and every call is made by a named person signed in to Elaichi. Elaichi can narrow that access, for example by restricting bulk lookups or email verification for a role or one person, and it never widens it. Nothing in RocketReach becomes reachable that was not reachable before.
Can I stop an agent from spending RocketReach credits or running bulk lookups?
Yes. Restrictions in Elaichi work per action, so you can restrict bulk lookups, email verification or any other RocketReach action for a role or for one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a RocketReach connection when someone leaves?
Offboarding that person in Elaichi ends their access to RocketReach at once, in every client. A shared RocketReach connection keeps working for everyone else on the team. If you disconnect RocketReach in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent in one step.
Does the RocketReach MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. RocketReach 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, Microsoft Copilot, 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 RocketReach?
Yes. Both let Claude, ChatGPT or Cursor use RocketReach. 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 RocketReach call.
How is Elaichi different from Composio for RocketReach?
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 RocketReach: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put RocketReach in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot