Clari MCP connector
The Clari connector brings Clari calls, scorecards, topics, deals, accounts and contacts into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client through one governed endpoint, with every person signed in as themselves.
- Connects with an API key
- Free 14-day trial
- No credit card
List this week's Clari calls with Acme and summarize the topics
Working in Clari with Elaichi
-
List all Clari calls
-
Get single Clari call by ID
-
List all Clari keyword topics
How to connect Clari to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Clari 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.
Clari 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.
Clari 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.
Clari 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.
Clari 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 Clari 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 Clari through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Clari is logged.
-
Sales
Catch the deal up after a call
Ask for the Clari call that just ended, then update the deal and the contact in one go, without opening Clari and clicking through each record.
-
Sales management
Review the week's calls before the pipeline meeting
Pull every Clari call a rep made this week, see which scorecards were filled in, and walk into the one to one already knowing where the coaching is needed.
-
Revenue operations
Clean up accounts and contacts in bulk
Find Clari accounts with stale owners or duplicate contacts and update or remove them as a batch, rather than one record at a time.
-
Enablement
See which topics come up on calls
List the Clari topics and keyword topics that appear most across recent calls, and spot the objections the team keeps hearing before the next training session.
-
Customer success
Prepare for a renewal conversation
Ask for every Clari call and deal tied to an account, then get a short summary of what the customer said last time before you join the renewal call.
-
Marketing
Build a contact list from real conversations
Pull the Clari contacts who joined calls on a given topic this quarter and create the missing ones so the campaign list reflects who actually showed up.
Try asking
- “List this week's Clari calls with Acme and summarize the topics”
- “Which Clari deals have no logged call in the last 30 days?”
- “Add Priya Shah at Northwind as a Clari contact”
What connecting Clari gets you
6 screens from Elaichi, each doing one job for your Clari account.
Ask Elaichi to work across your apps.
List this week's Clari calls with Acme and summarize the topics
Which Clari deals have no logged call in the last 30 days?
Add Priya Shah at Northwind as a Clari contact
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Clari calls in plain words.
Three starter prompts pull answers from live Clari calls, scorecards, deals and contacts.
Copy the endpoint
AI apps
Clari in Claude, ChatGPT and Cursor, one endpoint.
Every MCP client reaches Clari through one governed org endpoint, no SDK, no shared API key.
Tool catalog
20 Clari tools, no custom code to write.
Calls, scorecards, topics, users, accounts, contacts and deals, ready to use the moment you connect.
Toolboxes
Each team gets its own Clari toolbox.
Sales, enablement and revenue operations each see the Clari tools their work needs.
Shared connections
Share a Clari connection, never a credential.
One person connects Clari, teams and members work through it without seeing the API key.
Audit log
Every Clari call is on the record.
When, who, what happened, type and resource, for every deal or contact touched.
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.
Clari digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch calls
Clari
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
Clari
Queued
Workflows
A schedule starts the Clari digest, you approve.
Calls are fetched, grouped and drafted into a digest, approved, then posted back to Clari.
Clari health
Refreshed 4 minutes ago · every 15 minutes · from the calls collection
Calls
1,284 ↓ 12%
Deals
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 Americas 27%
Enablement 21%
Revenue operations 18%
Collections and dashboards
Clari numbers that nobody has to ask for.
Four metrics, 14 days of calls and a team breakdown, computed with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Clari
All three can connect Clari 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 Clari tools | Allow or restrict single Clari 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 Clari 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.
Clari tools for your AI agents
20 tools are ready to call through Elaichi's MCP endpoint the moment you connect Clari, 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 Clari to Claude?
Connect Clari in Elaichi first, which takes a Clari API key pasted into the connection form; 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 to Elaichi when Claude asks, and Clari calls, deals, accounts and contacts are available from the next message.
Does Clari work with ChatGPT and Cursor as well as Claude?
Yes. Clari is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client. The Elaichi Agent uses the same Clari connection too, so there is nothing to set up twice.
What can an AI agent actually do with my Clari data?
With Clari connected, an agent can find and read calls, scorecards, scorecard templates, topics, keyword topics and users, and it can create and list deals, accounts and contacts, including updating or removing them in bulk. In practice that means asking for last week's calls with a customer, logging a new contact after a meeting, or fixing a batch of account records. Short, concrete asks about Clari work better than long paragraphs.
Does connecting Clari give the AI everything in my Clari workspace?
No. A Clari connection carries the access of the Clari account whose API key was used, and every call is made by a person signed in to Elaichi as themselves. Elaichi can narrow that access with restrictions on roles or individuals, and it can never widen what Clari itself allows.
Can I stop an agent from deleting or changing things in Clari?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Clari calls and deals while restricting bulk deletes or bulk updates, on a role or on one person. A restricted Clari action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Clari connection when someone leaves?
Offboarding a person in Elaichi ends their access to Clari at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A shared Clari connection keeps working for everyone else on the team. If the whole connection should go, disconnecting Clari once in Elaichi removes it from every client at the same time.
Does the Clari MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Clari 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 Clari?
Yes. Both let Claude, ChatGPT or Cursor use Clari. 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 Clari call.
How is Elaichi different from Composio for Clari?
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 Clari: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Clari 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