Hyperbound MCP connector
Connect Hyperbound to Elaichi and Claude, ChatGPT or Cursor can review your calls, reps, teams and scorecards, ask Kota for coaching advice, and create bots and scorecards, with every call running as the person who signed in.
-
How it connects. Connects over OAuth. 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 Hyperbound to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Hyperbound once
-
Open Connections, choose Add connection, and pick Hyperbound.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Hyperbound. Hyperbound's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
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.
Hyperbound 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.
Hyperbound 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.
Hyperbound 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.
Hyperbound 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 Hyperbound 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 Hyperbound through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Get coaching on last night's practice call
A rep asks what went wrong on their discovery roleplay and gets the scorecard breakdown plus Kota's advice on the objection they fumbled, without opening Hyperbound.
-
Sales management
Spot which reps need attention this week
A manager asks which reps on the team scored lowest on cold calls this week and gets names, scores and the skills that slipped, ready for the one-on-one.
-
Enablement
Build a bot for the new pitch
An enablement lead describes the persona and objections they want reps to practice against and has the bot and its folder created in Hyperbound while they are still in the chat.
-
Enablement
Update a scorecard after the messaging change
When the talk track changes, the criteria on the affected scorecard are updated from a plain request instead of a click-through edit in Hyperbound.
-
Revenue operations
Compare team call performance across regions
RevOps asks how the EMEA and US teams compare on scorecard results this quarter and gets a summary they can paste into the pipeline review.
-
Recruiting
Review a candidate's screening roleplay
A hiring manager asks for the scores and highlights from a candidate's Hyperbound screening call and decides whether to move them forward.
Try asking
- “Which reps scored lowest on discovery calls this week?”
- “Ask Kota how I can handle the pricing objection better.”
- “Create a scorecard for the new cold call bot.”
Native MCP
Why connect Hyperbound's MCP server through Elaichi
Hyperbound builds and runs this MCP server. Elaichi sits in front of it, so Hyperbound's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Hyperbound's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT and Cursor reach Hyperbound's tools at https://api.elaichi.ai/mcp, the same address as every other connected app. Nobody adds Hyperbound's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Hyperbound sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Hyperbound's server. By default, a tool Hyperbound does not mark read-only or non-destructive counts as destructive, and over MCP it needs the "Delete data and remove access" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Hyperbound
Hyperbound builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Hyperbound team.
support.hyperbound.ai/articles/8696502812-hyperbound-mcp-server
Compare
Elaichi vs Zapier MCP vs Composio for Hyperbound
All three can connect Hyperbound 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 Hyperbound tools | Allow or restrict single Hyperbound 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 Hyperbound 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.
See it in Elaichi
What connecting Hyperbound gets you
5 screens from the product, each doing one job for your Hyperbound account.
The agent
Ask Hyperbound about any call in plain language.
Scores, reps and Kota coaching advice answered from live Hyperbound records, not an export.
- calls
- reps
- scorecards
- bots
Ask Elaichi to work across your apps.
Which reps scored lowest on discovery calls this week?
Ask Kota how I can handle the pricing objection better.
Create a scorecard for the new cold call bot.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Hyperbound endpoint for every AI client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Hyperbound toolbox.
Enablement manages scorecards and bots while reps keep to their own calls and coaching.
- Sales
- Sales management
- Enablement
- Revenue operations
ElaichiToolboxesShared connections
Share one Hyperbound connection without sharing a credential.
Teammates work through the connection as themselves and never see a token.
- Sales EMEA
- Sales US
- Enablement
- SDR team
ElaichiConnectionsAudit log
Every Hyperbound action lands in one audit log.
Who changed a scorecard, when, and on which record, answered in one place.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 the Hyperbound coaching digest.
Calls are fetched, grouped by rep, drafted by an agent, approved, then posted to Hyperbound.
Hyperbound digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch calls
Hyperbound
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
Hyperbound
Queued
Collections and dashboards
Hyperbound health numbers, refreshed on a schedule.
Calls scored, reps active and team breakdowns computed from Hyperbound with no model involved.
Hyperbound health
Refreshed 4 minutes ago · every 15 minutes · from the calls collection
Calls
1,284 ↓ 12%
Reps
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Calls created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales US 27%
Enablement 21%
SDR team 18%
FAQ
Frequently asked questions
How do I connect Hyperbound to Claude?
Connect Hyperbound in Elaichi first: pick it from the connector list, sign in to your Hyperbound account over OAuth, and approve. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Hyperbound is now available in Claude as you.
Does Hyperbound work with ChatGPT and Cursor as well as Claude?
Yes. The same Elaichi endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. Connect Hyperbound once in Elaichi and every client picks it up.
What can an AI agent actually do with my Hyperbound data?
It can look at your Hyperbound calls, reps, teams and scorecards and tell you how a call went, which reps are slipping and how teams compare. It can ask Kota for coaching advice on a specific call or skill. It can also create or update bots, scorecards and folders in Hyperbound from a plain request. Short, concrete asks work better than long paragraphs.
Does connecting Hyperbound give the AI everything in my workspace?
No. The AI acts as the person who signed in to Hyperbound, so it sees the calls, reps, teams and scorecards that person can already see and nothing more. Elaichi can narrow that further by role and restriction, and it never widens it beyond what Hyperbound itself allows.
Can I stop an agent from deleting or changing things in Hyperbound?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Hyperbound calls and scorecards while blocking changes to bots, scorecards or folders. A restricted action is left out of the tool list the AI client sees and cannot be called, whatever the prompt says.
What happens to a Hyperbound connection when someone leaves?
Offboarding someone in Elaichi ends their access to Hyperbound through every AI client at once. If they had shared a Hyperbound connection with a team, it keeps working for everyone else. Disconnecting Hyperbound once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Hyperbound MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Hyperbound 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 Hyperbound?
Yes. Both let Claude, ChatGPT or Cursor use Hyperbound. 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 Hyperbound call.
How is Elaichi different from Composio for Hyperbound?
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 Hyperbound: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Hyperbound 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.