Chorus MCP connector
The Chorus connector brings recorded sales calls, live meetings, email threads and engagement history into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so each person can search, pull up and export Chorus conversations inside their own access.
- Connects with an API key
- Free 14-day trial
- No credit card
List Chorus conversations recorded this week by team.
Working in Chorus with Elaichi
-
List all Chorus conversations
-
Get single Chorus conversation by ID
-
List all Chorus users
How to connect Chorus to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Chorus 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.
Chorus 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.
Chorus 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.
Chorus 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.
Chorus 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 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.
What teams do with Chorus through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Chorus is logged.
-
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?”
What connecting Chorus gets you
6 screens from Elaichi, each doing one job for your Chorus account.
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, Cursor or Microsoft Copilot
The agent
Ask about Chorus calls, get real answers.
Question Chorus conversations and users in plain language, answered from live records.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Chorus.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
79 Chorus tools ready without custom code.
Browse conversation, user and settings tools with every resource and method listed.
Toolboxes
Each team gets its own Chorus toolbox.
Curate toolboxes per team so Sales, Support and Enablement see different Chorus tools.
Shared connections
Teammates use Chorus without seeing credentials.
Every Chorus connection shows who connected it and which teams and members share it.
Audit log
Every Chorus call is on the record.
When, who, what happened, type and resource for each conversation and user call.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Chorus digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Chorus
Queued
Automations
A schedule turns Chorus calls into digests.
Fetch conversations, group them, draft a digest, get approval, post back to Chorus.
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%
Collections and dashboards
Chorus call numbers arrive without being asked.
Four metrics, 14 days of conversations created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Chorus
All three can connect Chorus 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 Chorus tools | Allow or restrict single Chorus 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 Chorus 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.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deletion of recordings, email threads or engagements. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client at the same time.
Does the Chorus MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Chorus 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 Chorus?
Yes. Both let Claude, ChatGPT or Cursor use Chorus. 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 Chorus call.
How is Elaichi different from Composio for Chorus?
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 Chorus: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Chorus 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