Connect once, use everywhere
Turn the apps your company already runs on into tools any AI can call. Connect each one a single time and reach it from Claude, ChatGPT, Cursor, and any MCP client, with nothing to reconnect when you switch.
In short
Elaichi gives your organization one MCP endpoint, at the same address for every organization: https://api.elaichi.ai/mcp.
Connect each SaaS account once, then point Claude, ChatGPT, Cursor or any MCP client at that address and sign in with OAuth. Each person connects once, with no token, secret or client ID to paste, and when you adopt a new client your accounts are already there, because they are connected to Elaichi rather than to one chatbot.
What changes
Today
With Elaichi
Who it is for
You work in ChatGPT, then Claude, then Cursor, and want the same apps ready in each one without setting them up again.
You want to roll out AI clients across the company without a server, token or setup per person per client to maintain.
You need internal APIs and apps outside the catalog reachable from the same place as everything else, under the same rules.
Real situations
An account executive connects Salesforce, Gmail and Slack once. They prospect in ChatGPT in the morning and review deals in Claude in the afternoon, and every account is already there in both, because neither client holds the connection.
An engineering team adds the one Elaichi address to Cursor. Each developer signs in with their own grant and reaches Jira and Sentry through it, with no MCP server to run per person and nothing to update when a connector changes.
A platform team adds their internal billing API as a custom connector from a JSON config. It answers through the same endpoint as every catalog app, under the same roles, restrictions and audit log.
Setup
Four steps, in the order an admin takes them.
Pick apps from the catalog and sign in through the hosted flow, or add a custom connector for anything else. Each account is connected once, to Elaichi.
Use https://api.elaichi.ai/mcp everywhere. On Claude Team and Enterprise an owner adds it as a custom connector for the organization, on ChatGPT Business an admin adds it as an app, and in Cursor it goes in the MCP settings.
Members connect and sign in with their own OAuth grant, choosing on Elaichi’s consent screen what the client may read, change, run or delete.
The same connected accounts answer in every client. Disconnect one client under Settings, Connected apps, and the others keep working.
Compare your options
| Aspect | Each client’s own connectors | A server per person | Elaichi |
|---|---|---|---|
| Setup | Each app, again in each client | A server per app, often per person | Each app once, to Elaichi |
| Adding an AI client | Connect everything again | Point it at each server and configure it | Add one address and sign in |
| Credentials | Held separately by each client | Kept in each server’s configuration | In the vault; clients hold an OAuth grant |
| Apps outside a catalog | Only what each client offers | Write and run your own server | A custom connector from a JSON config |
| Who maintains it | Each vendor, on its own schedule | Your team | Elaichi authors and runs its catalog connectors |
| Switching a client off | Disconnect each app in that client | Revoke keys in each server | Disconnect it; its next request is refused |
Under the hood
The specifics a careful reviewer checks, answered up front.
One address for everyone. https://api.elaichi.ai/mcp is the same for every organization. What changes from person to person is the grant, clamped by roles and restrictions, not the URL.
Nothing to paste. Clients register themselves through OAuth dynamic client registration with PKCE, so there is no client ID, secret or header to enter.
Connectors, already built. Elaichi authors and runs the connectors in its catalog, so the apps your team already uses are ready to connect, and a team can also bring its own remote MCP server under the same rules.
Scopes you choose. On the consent screen each person picks whether a client may read, change, run tools or delete, and delete is never pre-ticked. A client can be narrowed to chosen toolboxes, up to 50.
Share a capability, not a secret. A colleague works through your connection without ever seeing it.
Read the use caseDecide who can act, choose which tools each agent can use, and keep an attributed record of every call that runs.
Read the use caseThe right role from day one, and a clean exit in one action.
Read the use caseSee the whole picture in the product tour and the security model.
FAQ
No. You connect each account once to Elaichi. Claude, ChatGPT, Cursor and any other MCP client point at the same endpoint and sign in over OAuth. Switching clients does not reconnect anything.
https://api.elaichi.ai/mcp, the same for every organization. Copy it exactly, with no trailing slash and no query string. In the web app, Connect your AI client shows it with a copy button.
Claude, ChatGPT, Cursor and any other MCP client. Each person connects once and signs in with their own OAuth grant.
Yes. Custom connectors are authored from a JSON config and served from the same endpoint as every other app. You can also fork a public connector and pull its later changes through a review step.
No. There are no per-toolbox URLs and no embedded tokens. The endpoint is a single address for the whole organization; what varies per person is their grant, not the URL.
No. Connected tools are never listed one by one, however few there are. The model finds them with search_tools and runs them with execute_tool, so the list it sees stays the same size however many apps you connect.
Disconnecting it under Settings, Connected apps ends that client’s grant, and its next request is refused. Your other clients and your connected accounts are untouched.
Signing in to Elaichi happens in a browser, so it works from clients a person signs in to, such as Claude, ChatGPT and Cursor. A client running headless in CI, with no browser, cannot complete the OAuth sign-in.
Start a trial, connect a single account, and call it from both Claude and ChatGPT without connecting twice.
and any other MCP client, or the Elaichi Agent.
