“Which Jira bugs mention the checkout page?”
Cursor without a server per developer
The team adds the one Elaichi link to Cursor. Each developer signs in as themselves and reaches Jira and Notion through it, with no server to run.
Sign in to each work app one time. Then use it from ChatGPT, Claude, Cursor or Microsoft Copilot. Add another AI app later, and your apps are already there.
Draft a follow-up to Acme Corp from my call notes.
ECThe same apps as in ChatGPT · checking 3 with Elaichi
Your draft to Dana Lee is in Gmail. It covers the SSO fix and the October 31 renewal date.
Different people, different AI apps, the same connected apps.
“Which Jira bugs mention the checkout page?”
The team adds the one Elaichi link to Cursor. Each developer signs in as themselves and reaches Jira and Notion through it, with no server to run.
“Any open Zendesk tickets from Acme Corp?”
IT adds Elaichi to a Copilot Studio agent once, and the Zendesk and Slack accounts connected to Elaichi are there, the same ones Jake uses in Claude.
“How many accounts are past due in our billing system?”
The platform team adds the company’s billing API as a custom connector from a JSON config. It works through the same link as every other app, under the same roles, restrictions and audit log.
How connecting AI to your apps usually goes
With Elaichi
In the order an admin takes them.
Pick apps from the catalog and sign in to each one once. On Gold and Black, add a custom connector for anything else.
In Claude Team and Enterprise an owner adds it as a custom connector, in ChatGPT Business an admin adds it as an app, Cursor takes it in its MCP settings, and Microsoft Copilot reaches it through a Copilot Studio agent.
https://api.elaichi.ai/mcp
The same for every organization.
Everyone signs in with their own account and picks what the AI app may do on Elaichi’s consent screen.
The same connected accounts answer in every AI app. Disconnect one under Settings, Connected apps, and the others keep working.
Elaichi gives every organization the same MCP address. Connect each work account once, then add that address to ChatGPT, Claude or Cursor, or to Microsoft Copilot through a Copilot Studio agent, and sign in with OAuth. There is no token, secret or client ID to paste. Each person connects each AI app once, and when they add another, their accounts are already there, because they are connected to Elaichi, not to one chatbot.
One address for everyone. Every organization uses the same address. What changes from person to person is the sign-in grant, limited by roles and restrictions, not the URL.
Nothing to paste. AI apps register themselves through OAuth dynamic client registration with PKCE, so there is no client ID, secret or header to enter.
Connectors, already built. Elaichi builds and runs most connectors in its catalog and governs vendors’ own MCP servers for the rest. On Gold and Black, a team can also bring its own remote MCP server under the same rules.
Scopes you choose. On the consent screen each person picks what an AI app may do. “Use your connected apps” runs every tool they can use, deletes in your apps included; the other boxes cover Elaichi’s own data, and delete is never pre-ticked. An AI app can also be held to up to 50 chosen toolboxes.
| Aspect | Each AI app’s own connectors | A server you run | Elaichi |
|---|---|---|---|
| Setup | Each app, in each AI app | A server for each app you add | Each app once, to Elaichi |
| Adding an AI app | Connect the apps there too | Point it at each server | Add one link and sign in |
| Logins | Set up in each AI app | In each server’s settings | Stored encrypted in Elaichi; AI apps hold only a sign-in grant |
| Apps outside a catalog | Add each custom server in each AI app | Write and run your own server | A custom connector from a JSON config, on Gold and Black |
| Who runs it | Each vendor | Your team | Elaichi runs most catalog connectors; vendors run their own MCP servers, which Elaichi governs |
| Turning an AI app off | Disconnect each app in that AI app | Revoke keys in each server | Disconnect it; it stops on its next request |
Share an app with your team, not the login. Each person uses it from their own AI.
Read moreBuild a toolbox once, and the whole team can use the same tools and steps in each AI app they use.
Read moreDecide what each role or person’s AI can do, down to single actions, and see every call that runs.
Read moreSee the whole picture in the product tour and the security model.
No. You connect each account once, to Elaichi. Each AI app then signs in to the same address, once per person, and switching apps reconnects nothing.
ChatGPT, Claude and Cursor, Microsoft Copilot through a Copilot Studio agent, and any other MCP client that supports OAuth dynamic client registration, PKCE and a sign-in in the browser.
For one person in one AI app, they may be all you need. Each AI app keeps its own connections, so a second app means connecting the same accounts again. Connected to Elaichi, your accounts are already there in every AI app you add, under one set of roles and restrictions and one audit log.
The MCP address on this page, which is 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.
Yes, on Gold and Black. Custom connectors are built from a JSON config and served from the same address as every other app. You can also fork a public connector and pull in its later changes after a review.
No. There are no per-toolbox URLs and no tokens in the URL. One address serves the whole organization; what differs per person is their sign-in grant.
No. Connected tools are never listed one by one. The AI 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 app’s access from its next request. Your other AI apps and your connected accounts are untouched.
Signing in to Elaichi needs a person in a browser, so it works from AI apps a person signs in to. A program running with no browser, as in CI, can’t complete the sign-in.
Start a trial, connect one account, and use it from both ChatGPT and Claude without connecting twice.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp