Skip to content

Connectors / Conversational Intelligence

Conversational Intelligence MCP connectors for Claude, ChatGPT and Cursor

10+ Conversational Intelligence connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.

https://api.elaichi.ai/mcp The same for every user.
  • Their own access. An agent never gets more than the person it acts for.

  • One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.

The connectors

Conversational Intelligence connectors in the catalog

Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.

14 connectors

Browse all 600+ connectors →

In practice

What teams do with Conversational Intelligence connectors

Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.

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.

  • Translate a proposal before it goes out

    Take the English proposal or follow-up note and turn it into the customer's language, then check which language a reply came back in before anyone answers.

  • Catch up before the next call

    Ask what was promised on the last three Circleback calls with an account and get the action items, open questions and who owns each, before you dial in.

Support

  • Turn recorded calls into searchable text

    Send a customer call recording to Groq for transcription and get back a text version the desk can search, quote, and attach to the ticket.

  • Find where a customer first described the bug

    Search transcripts for the error or feature a customer mentioned and read the exact exchange. Share that meeting with the engineer who picks up the ticket.

  • Find every call where a bug came up

    Search meeting content for a product name or an error message, and pull the matching conversations together for the engineering handoff.

Product

  • Turn a planning meeting into tracked work

    Read the transcript of the planning session, list every commitment that was made and check which action items in Fellow are still unassigned.

  • Find what customers said about a feature

    Search across recent customer call summaries for mentions of a specific feature or complaint, and collect the exact quotes for the roadmap discussion.

  • Find feature requests buried in customer calls

    Search across Granola notes for mentions of a feature or a pain point and get a list of which customers raised it and when.

Operations

  • Answer who has access to which OpenAI project

    Pull a plain list of OpenAI projects with their members, service accounts, and keys, and archive projects that have gone quiet, so the organization stays tidy and reviewable.

  • Answer who has access to what

    Ask for every Anthropic user, their organization role, and the workspaces they belong to. Hand the list to an auditor or a manager without exporting anything by hand.

  • Clear out old transcripts on schedule

    List transcripts older than your retention period and delete them, so recordings of past hires and former customers are not kept longer than policy allows.

Once it is connected

Things to ask

Each of these is answered against the access the person asking already has, in the Conversational Intelligence account you connected.

  • Which Anthropic workspaces have no members right now?

    Anthropic

  • List last week's AssemblyAI transcripts and their durations.

    AssemblyAI

  • List Chorus conversations recorded this week by team.

    Chorus

  • What action items came out of yesterday's Acme renewal call?

    Circleback

  • Summarize this week's Fathom meetings for the Sales team

    Fathom

  • Summarize yesterday's customer calls and list every open action item.

    Fellow

  • Summarize yesterday's call with Acme and list every commitment we made.

    Fireflies.ai

  • Summarize action items from this week's customer calls.

    Grain

The tools

What an agent can call in Conversational Intelligence

Connectors
10+

in the Conversational Intelligence catalog

Tools
515

callable the moment you connect

Hosted sign-in
7

connect with nothing to register

Of those 515 tools, 10% delete something. Restricting an agent to reads is not a promise here, it is 218 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.

Read 42%
218 tools · list, get, search
Write 27%
139 tools · create, update, send
Delete 10%
54 tools · delete, remove, archive
Other 20%
104 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector above answers here.

Every Conversational Intelligence connector, by depth

Tool counts are what the connector exposes today; the split is what those tools do.

Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect. API key and App credentials mean an admin pastes them once, with nothing to register.

Conversational Intelligence connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
OpenAI 157 API key
Anthropic 117 API key
Chorus 79 API key
Sarvam 28 API key
Circleback 21 Hosted
Groq 21 API key
Fireflies.ai 19 Hosted
Fellow 18 Hosted
Krisp 18 Hosted
AssemblyAI 14 API key
Fathom 11 Hosted
Granola 7 API key
Plaud 5 Hosted
Grain Hosted

FAQ

Frequently asked questions

How many Conversational Intelligence connectors does Elaichi have?

10+ Conversational Intelligence connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.

Can Claude, ChatGPT and Cursor all use Conversational Intelligence connectors?

Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor or any MCP client connects to that same address with OAuth, while the Elaichi Agent reaches the same tools inside the app. Connecting a Conversational Intelligence account once makes it reachable from every one of them.

Do Conversational Intelligence connectors work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Conversational Intelligence connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.

Do Conversational Intelligence connectors need me to bring my own OAuth app?

No. 7 of the Conversational Intelligence connectors use Elaichi's hosted sign-in, with nothing to register. 7 connect with an API key or app credentials that an admin pastes once, with no app to register. Nothing in this category asks you to register an OAuth app before you start.

Can I stop an agent from writing to Conversational Intelligence tools?

Yes. Tool restrictions apply at role and individual level, and a restricted tool is left out of the model's tool list and cannot be called. Read-only access to a Conversational Intelligence connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared Conversational Intelligence connection?

The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential.

Nearby

Teams that connect Conversational Intelligence usually connect these too

Put Conversational Intelligence connectors in front of your team

14 days on Gold, no credit card. Connect one and pick what each team can call.

Works with
Claude ChatGPT Cursor 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.