# 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.

Source: https://elaichi.ai/connectors/clari/

## Facts

| | |
| --- | --- |
| Application | Clari |
| Category | Sales Intelligence |
| AI tools | 20 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Clari is connected

- 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

## Connect Clari in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Clari.
2. Optionally set Share with, then press Connect.
3. Paste a Clari API key. One person generates a token in Clari and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Clari tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Clari MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Clari MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Clari tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Clari through Elaichi

### Catch the deal up after a call

Sales. 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.

### Review the week's calls before the pipeline meeting

Sales management. 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.

### Clean up accounts and contacts in bulk

Revenue operations. Find Clari accounts with stale owners or duplicate contacts and update or remove them as a batch, rather than one record at a time.

### See which topics come up on calls

Enablement. 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.

### Prepare for a renewal conversation

Customer success. 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.

### Build a contact list from real conversations

Marketing. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Clari connection?

Yes. One person connects Clari with the API key and shares the connection with a team in Elaichi, and nobody else ever handles or sees that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Clari call, deal or contact that was read or changed.

### 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.

## All 20 Clari tools

Every tool below is callable through https://api.elaichi.ai/mcp once Clari is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Clari call** (Create). Create a call in Clari Copilot by submitting an audio recording for transcription and analysis. Returns: call_id, error. Required: source_id, type, call_time, audio_url. One call per request — iterate to upload calls in bulk (e.g. migrations from Zoom or Twilio).
- **List all Clari calls** (List). List Clari Copilot calls filtered by user, attendee, topic, status, type, source, time range, or duration, with sort options. Returns: id, source_id, title, users, externalParticipants, joinedParticipants, status, type, time, icaluid, calendar_id, audio_url, video_url, and 19 more. Max 100 calls per page; use call-details for transcript.
- **Get single Clari call by ID** (Get). Get the full details of a single Clari Copilot call by id, including its transcript, summary, and live deal stage. Returns: id, source_id, title, users, externalParticipants, joinedParticipants, status, bot_not_join_reason, type, time, icaluid, metrics, deal_stage_live, transcript, summary, competitor_sentiments, and 16 more. Required: id.
- **List all Clari keyword topics** (List). List keyword topics in Clari Copilot. Returns the collection of keyword topics — basic tags such as 'Pricing' or 'Budget' — without the rich metadata returned by the Smart Topics endpoint.
- **List all Clari scorecard templates** (List). List all scorecard templates in Clari Copilot along with their details. Returns: id, customer_id, name, type, questions.
- **List all Clari scorecards** (List). List Clari scorecards for calls, filterable by time range, rep, and scorer. Returns: id, type, rep, scorer, template_id, call_id, total_score, remark, questions_score. Max 100 per page.
- **List all Clari topics** (List). List all unique keyword topics in Clari Copilot. Returns each topic with topic_id, topic_name, type, team_ids, custom_topic, and keyword_topic.
- **List all Clari users** (List). List the current users in Clari Copilot. Returns each user's id, email, name, role, is_recording, and manager_id.
- **Create a Clari account** (Create). Create a new account in Clari Copilot CRM. Returns the created account including id, crm_id, name, phones, address, and custom_fields.
- **List all Clari accounts** (List). Get an account in Clari Copilot CRM by id. Returns: id, crm_id, name, phones, description, website, address, city, state, country, zip, custom_fields. Required: id.
- **Clari accounts bulk delete** (Delete). Delete an account in Clari Copilot CRM by id. Returns the deleted account including id, crm_id, name, and address.
- **Clari accounts bulk update** (Update). Update an account in Clari Copilot CRM. Returns the updated account including id, crm_id, name, phones, address, and custom_fields.
- **Create a Clari contact** (Create). Create a contact in Clari's CRM with CRM ids, name, job title, phones, emails, stage, and custom fields. Returns the created contact including id, crm_id, first_name, last_name, emails, and custom_fields.
- **List all Clari contacts** (List). Get a contact from Clari's CRM by id. Returns: id, crm_id, account_crm_id, first_name, last_name, job_title, phones, stage, reason, emails, is_lead, custom_fields. Required: id.
- **Clari contacts bulk delete** (Delete). Delete a contact from Clari's CRM. Returns the deleted contact including id, crm_id, first_name, last_name, and emails.
- **Clari contacts bulk update** (Update). Update a contact in Clari's CRM, including name, job title, emails, phones, stage, and custom fields. Returns the updated contact including id, crm_id, first_name, and last_name.
- **Create a Clari deal** (Create). Create a deal in Clari. Returns the created deal including id, crm_id, deal_name, amount, stage, close_date, and probability.
- **List all Clari deals** (List). Get a Clari deal by id. Returns the deal including id, crm_id, deal_name, amount, stage, close_date, and probability. Required: id.
- **Clari deals bulk delete** (Delete). Delete a Clari deal. Returns the deleted deal including id, crm_id, deal_name, amount, stage, and close_date.
- **Clari deals bulk update** (Update). Update a Clari deal. Returns the updated deal including id, crm_id, deal_name, amount, stage, and close_date.
