Skip to content

Connectors / IPAAS

IPAAS MCP connectors for Claude, ChatGPT and Cursor

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

IPAAS connectors in the catalog

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

5 connectors

Browse all 600+ connectors →

In practice

What teams do with IPAAS connectors

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

Operations

  • Clean up stale sessions and churned accounts

    Bulk delete abandoned Nango connect sessions and remove connections for customers who have left, keeping the workspace tidy and the connection count accurate.

  • Check overnight automation runs before standup

    Ask which Gumloop automations ran last night, which finished cleanly, and which need a second look, then open the details of any single run without leaving the chat.

  • Check which workflows are live before a release

    Ask for the full list of Tavio workflows and pull up any one by name to confirm what it does and which environment it runs in before you change anything.

Support

  • Log a ticket update through Zapier

    After a customer call, run a Zapier write action to update the ticket or post a note in the desk tool your team already uses.

  • Find the scenario that routes tickets

    Ask which Make scenario handles ticket routing, what it is connected to and when it last ran, without digging through the Make dashboard.

  • Reconnect a customer whose connection stopped working

    When a customer reports that their linked account has gone stale, pull up their Nango connection, start a reconnect session, and send them the link without opening the Nango dashboard.

Marketing

  • Find the flow that already does this

    Before anyone rebuilds a lead enrichment or content flow, list the Gumloop flows and workbooks the team already has and see what each one is for.

  • Add a new lead to the right list

    Run a Zapier write action that drops a new contact into your email or ads platform the moment it comes up in a conversation.

  • Check which campaign automations ran overnight

    Ask which Make scenarios ran since yesterday and which ones stopped with an error, so a broken lead handoff is caught before the morning standup.

IT

  • Add a new hire to Tavio in one step

    Create the Tavio user, confirm their details, and update their record later when their role changes, all from the chat window where you already work.

  • See which Zapier connections are live

    List the app connections behind your Zapier account, review the ones that need attention, and fetch the configuration link when an app needs to be reauthorized.

  • Review every active scenario in one place

    List the scenarios running in each Make team, see who owns them and spot the ones nobody has touched in months.

Once it is connected

Things to ask

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

  • List the Gumloop agents created this month.

    Gumloop

  • Run the lead sync scenario now and tell me how it went.

    Make

  • List every Nango integration and how many connections each has.

    Nango

  • List all Tavio environments and who owns each one.

    Tavio

  • Which Zapier actions are enabled for our CRM?

    Zapier

The tools

What an agent can call in IPAAS

Connectors
5+

in the IPAAS catalog

Tools
137

callable the moment you connect

Hosted sign-in
2

connect with nothing to register

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

Read 38%
52 tools · list, get, search
Write 26%
36 tools · create, update, send
Delete 9%
13 tools · delete, remove, archive
Other 26%
36 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector above answers here.

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

IPAAS connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
Nango 53 API key
Gumloop 38 API key
Tavio 30 API key
Zapier 16 Hosted
Make Hosted

FAQ

Frequently asked questions

How many IPAAS connectors does Elaichi have?

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

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

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

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

Whose access does an agent get on a shared IPAAS 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.

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