HeyReach MCP connector
Connect HeyReach to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent can list campaigns, start, pause, and resume them, add leads, and check LinkedIn account status, each person signed in as themselves.
- Connects with an API key
- Free 14-day trial
- No credit card
Which HeyReach campaigns are paused right now?
Working in HeyReach with Elaichi
-
List all HeyReach campaigns
-
Get single HeyReach campaign by ID
-
HeyReach campaigns get sequence
How to connect HeyReach to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
HeyReach 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.
HeyReach 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.
HeyReach 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.
HeyReach 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.
HeyReach 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 HeyReach 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 HeyReach through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in HeyReach is logged.
-
Sales
Add new leads to a campaign
Paste a list of prospects from a call or a trade show and have them added to the right HeyReach campaign, with the sequence and schedule already in place.
-
SDR
Pause outreach when a prospect replies
Ask the agent to stop a lead in a campaign the moment they book a meeting, so nobody gets a follow-up message after they have already said yes.
-
Sales leadership
Check which campaigns are running today
Get a plain answer on which HeyReach campaigns are active, paused, or waiting to start, without opening the dashboard.
-
Marketing
Spin up a campaign from a template
Create a new HeyReach campaign from an approved template, update the sequence wording, and set the sending schedule in one conversation.
-
RevOps
Keep LinkedIn accounts healthy and assigned
Check the status of every connected LinkedIn account, see which campaigns each one is attached to, and move accounts between campaigns when someone is out.
-
Agency
Resume a client campaign after review
When a client signs off on new messaging, update the campaign settings and resume it, with the change recorded against your name.
Try asking
- “Which HeyReach campaigns are paused right now?”
- “Add these five leads to the Q3 founders campaign.”
- “Which LinkedIn accounts need attention before Monday's launch?”
What connecting HeyReach gets you
6 screens from Elaichi, each doing one job for your HeyReach account.
Ask Elaichi to work across your apps.
Which HeyReach campaigns are paused right now?
Add these five leads to the Q3 founders campaign.
Which LinkedIn accounts need attention before Monday's launch?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about HeyReach campaigns in plain language.
Three starter prompts pull live campaign, lead, and LinkedIn account answers from HeyReach.
Copy the endpoint
AI apps
One endpoint brings HeyReach to every client.
Claude, ChatGPT and Cursor reach HeyReach through one governed endpoint, no SDK, no shared key.
Tool catalog
69 HeyReach tools, no code to write.
Campaigns, leads, sequences and LinkedIn accounts, covered in a catalog you never had to build.
Toolboxes
Every team gets its own HeyReach toolbox.
SDRs, account executives and marketing each work from a toolbox scoped to their team.
Shared connections
Teammates use HeyReach without touching the key.
One person connects HeyReach, shares it with teams, and nobody else ever sees the credential.
Audit log
Every HeyReach action names who did it.
When, who, what happened and which campaign or lead, 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.
HeyReach digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch campaigns
HeyReach
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
HeyReach
Queued
Workflows
A schedule starts the work, a person approves.
HeyReach campaign leads are fetched, grouped, drafted into a digest, approved, then posted back.
HeyReach health
Refreshed 4 minutes ago · every 15 minutes · from the campaigns collection
Campaigns
1,284 ↓ 12%
Leads
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Campaigns created
Last 14 days
By team
Share of activity
Outbound EMEA 34%
Outbound NA 27%
Marketing 21%
Agency clients 18%
Collections and dashboards
HeyReach numbers refresh without anyone asking.
Four metrics, 14 days of leads added, and a breakdown by team, computed without a model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for HeyReach
All three can connect HeyReach 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 HeyReach tools | Allow or restrict single HeyReach 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 HeyReach 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.
HeyReach tools for your AI agents
69 tools are ready to call through Elaichi's MCP endpoint the moment you connect HeyReach, 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 HeyReach to Claude?
Open Elaichi, choose HeyReach, and paste your HeyReach API key when asked. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint.
Does HeyReach work with ChatGPT and Cursor as well as Claude?
Yes. Once HeyReach 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 HeyReach once and every client picks it up.
What can an AI agent actually do with my HeyReach data?
It can list your HeyReach campaigns, tell you which are running or paused, start, pause, or resume them, and change a campaign's sequence, settings, or schedule. It can add leads to a campaign, stop a lead who has replied, and check which LinkedIn accounts are connected and whether they are healthy. Short, concrete asks work better than long paragraphs.
Does connecting HeyReach give the AI everything in my workspace?
An agent working through HeyReach only sees what the person who signed in to Elaichi can see, and the HeyReach API key behind the connection sets the outer limit. Elaichi can narrow that access with roles and restrictions, and it never widens it. If you cannot delete a LinkedIn account in HeyReach today, an agent cannot do it for you.
Can I stop an agent from deleting or changing things in HeyReach?
Yes. Restrictions in Elaichi work per action, so you can allow reading HeyReach campaigns while restricting deleting LinkedIn accounts or changing a sequence, on a role or on 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 HeyReach connection when someone leaves?
Offboarding a person in Elaichi ends their access to HeyReach at once, across every client they used. A HeyReach connection shared with a team keeps working for everyone else. If you disconnect HeyReach in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client in one step.
Does the HeyReach MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. HeyReach 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 HeyReach?
Yes. Both let Claude, ChatGPT or Cursor use HeyReach. 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 HeyReach call.
How is Elaichi different from Composio for HeyReach?
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 HeyReach: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put HeyReach 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