Conversational Intelligence
Chorus MCP connector
The Chorus connector brings recorded sales calls, live meetings, email threads and engagement history into Claude, ChatGPT, Cursor and any MCP client, so each person can search, pull up and export Chorus conversations inside their own 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 Chorus to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Chorus once
-
Open Connections, choose Add connection, and pick Chorus.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Chorus API key. One person generates a token in Chorus 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.
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.
Connect Chorus to 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.
Connect Chorus to 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.
Connect Chorus to 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 Chorus 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 Chorus through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Pull up last week's calls with an account
Ask for every Chorus conversation with a prospect before the next meeting and review what was covered, who joined, and how long it ran.
-
Sales
Get Chorus into a meeting you forgot
Have Chorus join a live call that was scheduled outside the usual calendar flow, so the recording lands with the rest of the deal history.
-
Sales leadership
Review a rep's conversations from the month
List the calls a rep held in a period, open the ones that matter, and prepare coaching notes without clicking through the Chorus library one recording at a time.
-
Revenue operations
Export conversations for a deal review
Export a set of Chorus conversations by account or date range and hand the files to a deal desk or a data warehouse team.
-
Customer success
Read the email thread behind a renewal
Find the Chorus email threads and engagements tied to a customer, and check what was promised before a renewal or escalation call.
-
Revenue operations
Clean up test and duplicate recordings
Find Chorus conversations and engagements that were recorded by mistake and remove them, with each deletion written to the audit log under the person who asked for it.
Try asking
- “List Chorus conversations recorded this week by team.”
- “Summarize the last Chorus conversation with Northwind.”
- “Which Chorus users recorded the most calls last month?”
AI tools
Chorus tools for your AI agents
79 tools are ready to call through Elaichi's MCP endpoint the moment you connect Chorus, 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 Chorus gets you
6 screens from the product, each doing one job for your Chorus account.
The agent
Ask about Chorus calls, get real answers.
Question Chorus conversations and users in plain language, answered from live records.
- conversations
- users
- exports
- settings
Ask Elaichi to work across your apps.
List Chorus conversations recorded this week by team.
Summarize the last Chorus conversation with Northwind.
Which Chorus users recorded the most calls last month?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Chorus.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
79 Chorus tools ready without custom code.
Browse conversation, user and settings tools with every resource and method listed.
- List all Chorus conversations
- Get single Chorus conversation by ID
- Chorus conversations bulk
- Delete a Chorus conversation by ID
Toolboxes
Each team gets its own Chorus toolbox.
Curate toolboxes per team so Sales, Support and Enablement see different Chorus tools.
- Sales
- Sales enablement
- Customer success
- Support
Shared connections
Teammates use Chorus without seeing credentials.
Every Chorus connection shows who connected it and which teams and members share it.
- Sales EMEA
- Sales AMER
- Enablement
- Customer success
Audit log
Every Chorus call is on the record.
When, who, what happened, type and resource for each conversation and user call.
- 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 turns Chorus calls into digests.
Fetch conversations, group them, draft a digest, get approval, post back to Chorus.
Chorus digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch conversations
Chorus
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
Chorus
Queued
Collections and dashboards
Chorus call numbers arrive without being asked.
Four metrics, 14 days of conversations created and a team breakdown, refreshed on schedule.
Chorus health
Refreshed 4 minutes ago · every 15 minutes · from the conversations collection
Conversations
1,284 ↓ 12%
Users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Conversations created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales AMER 27%
Enablement 21%
Customer success 18%
FAQ
Frequently asked questions
How do I connect Chorus to Claude?
Connect Chorus in Elaichi first, which asks for a Chorus API key and nothing else, so 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 as the endpoint. Sign in with your Elaichi account when Claude asks, and Chorus conversations, emails and engagements are available in that chat.
Does Chorus work with ChatGPT and Cursor as well as Claude?
Yes. Once Chorus is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect Chorus once and every client you use picks it up.
What can an AI agent actually do with my Chorus data?
An agent connected to Chorus can list and open recorded conversations, find calls with a particular account or from a particular period, and export conversations for review. It can also read email threads and engagements linked to a customer, see which live meetings are running, have Chorus join a call, and remove recordings that should not be there. Chorus offers many actions, so short concrete asks such as "calls with Acme in March" work better than long paragraphs.
Does connecting Chorus give the AI every recording in the workspace?
No. Every request runs inside the access of the person who signed in, so an agent sees only the Chorus conversations, emails and engagements that person can already see in Chorus. Elaichi can narrow that further, for example to reading only, but it can never widen it beyond what Chorus itself allows.
Can I stop an agent from deleting or changing things in Chorus?
Yes. Restrictions in Elaichi apply per action, so you can allow reading and exporting Chorus conversations while blocking deletion of recordings, email threads or engagements. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to a Chorus connection when someone leaves?
Offboarding a person in Elaichi ends their access to Chorus through every client at once. If they connected a shared Chorus account, it keeps working for the rest of the team. Disconnecting Chorus once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put Chorus in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.