Skip to content

Connectors / Artificial Intelligence

Artificial Intelligence MCP connectors for Claude, ChatGPT and Cursor

20+ Artificial 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.

In practice

What teams do with Artificial Intelligence connectors

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

Support

  • Find out what happened to a customer's app

    Look up an app by name, read its current configuration and recent actions, and tell the customer exactly what changed and when.

  • Confirm LangChain is healthy during an incident

    Check LangChain's health status and the metadata on the affected session so you can tell customers what is going on with confidence.

  • Refresh phone menu prompts the same day

    Describe the new hold message or menu options and get the audio back ready to upload. When a policy changes on Monday, the greeting changes on Monday too.

Operations

  • Clean out bad labels in bulk

    Ask to remove a list of annotation objects that failed review, once the removal has been approved and the objects are confirmed.

  • Redeem credit codes and track the balance

    Redeem a credit code the moment it arrives and list past redemptions so the team knows how much credit is left to spend.

  • Keep the bot inventory straight

    Get a plain list of every Botpress bot in the workspace with its ID, so the runbook and the on-call sheet match what is actually deployed.

Product

  • Tighten a prompt after user feedback

    Describe the change you want, review the new prompt version, and set it as the default once you are happy with it.

  • Fork a project to try a new idea

    Copy an existing project into a fresh fork so a new detection experiment starts from real labeled data instead of an empty dataset.

  • Stand up a new agent from a brief

    Describe the agent you need in plain language and have it created in ElizaOS with the right name and character, then start it when you are ready.

Engineering

  • Pick the right model before you build

    Ask which Fal.ai models are available for a task, compare their pricing side by side, and get a cost estimate for the volume you expect before anyone writes a line of code.

  • Check an index before a release

    Ask which indices exist, pull up the settings on one, and browse a sample of its records to confirm the latest push landed as expected.

  • Run large prompt batches overnight

    Queue a batch of thousands of prompts, list what is running, pull results by batch when they land, and check dataset usage before the bill arrives.

Once it is connected

Things to ask

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

  • Which AirOps apps ran the most executions last week?

    AirOps

  • Which Algolia indices gained the most records this week?

    Algolia

  • List all Botpress hub integrations added this month.

    Botpress

  • Summarize the latest experiment in the checkout project

    Braintrust

  • Show me open help desk tickets from this morning

    Chatbase

  • Which Chatvolt agents handled the most conversations this week?

    Chatvolt

  • Summarize last week's Cohere embed jobs by status.

    Cohere

  • List every DigitalOcean account key and who created it.

    DigitalOcean

The tools

What an agent can call in Artificial Intelligence

Connectors
20+

in the Artificial Intelligence catalog

Tools
3,221

callable the moment you connect

Hosted sign-in
4

connect with nothing to register

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

Read 40%
1,285 tools · list, get, search
Write 32%
1,015 tools · create, update, send
Delete 9%
284 tools · delete, remove, archive
Other 20%
637 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector above answers here.

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

Artificial Intelligence connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
DigitalOcean 683 API key
Supervisely 455 API key
LangChain 382 API key
ElevenLabs 339 API key
Portkey 239 API key
Fireworks AI 206 API key
Botpress 198 API key
Chatvolt 113 API key
Roboflow 103 API key
ElizaOS 82 API key
Fal.ai 74 API key
Algolia 57 API key
Imagga 50 API key
Verbit 46 API key
AirOps 43 API key
Braintrust 43 Hosted
Cohere 40 API key
Warp 27 API key
OpenPipe 23 API key
Z.ai 14 API key
Hugging Face 4 Hosted
Chatbase Hosted
Tavily Hosted

FAQ

Frequently asked questions

How many Artificial Intelligence connectors does Elaichi have?

20+ Artificial 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 Artificial 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 Artificial Intelligence account once makes it reachable from every one of them.

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

Yes. Artificial 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 Artificial Intelligence connectors need me to bring my own OAuth app?

No. 4 of the Artificial Intelligence connectors use Elaichi's hosted sign-in, with nothing to register. 19 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 Artificial 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 Artificial Intelligence connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared Artificial 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 Artificial Intelligence usually connect these too

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