Skip to content

Connectors / Conversational Intelligence

Conversational Intelligence MCP connectors for Claude, ChatGPT and Cursor

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

8 connectors

Browse all 400+ 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.

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.

  • Pull the details out of a scanned form

    Send a batch of invoices, applications or field reports through Sarvam document intelligence and get the contents back as text you can work with.

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 prospect call into English

    Upload a demo recording in another language and have Groq translate it into English text so the whole team can read what was promised.

  • Turn a discovery call into notes

    Upload the recording after a call, get the transcript back, and ask for the objections, next steps, and who promised what, ready to paste into the deal.

Support

  • Turn a troubleshooting call into a ticket

    Take the transcript of a screen-share session with a customer and draft a clear write-up of the problem, the steps tried and what was agreed.

  • Transcribe a customer call in any Indian language

    Upload the recording of a Hindi, Tamil or Marathi support call and get back a transcript, or an English translation of it, ready to paste into the ticket.

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

IT

  • Add a new hire to the right OpenAI projects

    Ask for a new teammate to be added to the OpenAI organization and given membership in the projects their team uses, with the role you name. What used to be three admin screens becomes one request.

  • Invite a new hire and place them

    Send the Anthropic organization invite, then add the person to the right workspace with the right role once they accept. No console clicking, no waiting on an admin.

  • Offboard someone from Anthropic in one ask

    Remove a departing colleague from every Anthropic workspace they belong to and delete their user record. Confirm afterward that nothing is still assigned to them.

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

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

    Fathom

  • Summarize the customer calls in my Granola notes this week

    Granola

  • Summarize this week's Groq transcriptions by team.

    Groq

  • Which OpenAI projects have no project users left?

    OpenAI

  • Summarize this week's Sarvam speech to text jobs.

    Sarvam

The tools

What an agent can call in Conversational Intelligence

Connectors
5+

in the Conversational Intelligence catalog

Tools
356

callable the moment you connect

Hosted sign-in
8

connect with nothing to register

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

Read 42%
148 tools · list, get, search
Write 31%
110 tools · create, update, send
Delete 12%
42 tools · delete, remove, archive
Other 16%
56 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.

Conversational Intelligence connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
OpenAI 157 Hosted
Chorus 79 Hosted
Anthropic 43 Hosted
Sarvam 28 Hosted
Groq 21 Hosted
AssemblyAI 14 Hosted
Fathom 7 Hosted
Granola 7 Hosted

FAQ

Frequently asked questions

How many Conversational Intelligence connectors does Elaichi have?

5+ 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, any MCP client and the Elaichi Agent all connect to that same address with OAuth. 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. Every Conversational Intelligence connector in the catalog connects through Elaichi's hosted sign-in, so there is nothing to register 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 never advertised to the model, so it cannot be called or guessed at from the tool list. 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.