Skip to content

ChatGPT

Connect ChatGPT to Elaichi once. From then on, every app your organization has connected in Elaichi — and every tool you are allowed to use — is reachable from a ChatGPT conversation.

Where to find the endpoint: in the Elaichi web app, open Connect your AI client and copy the endpoint shown there.

Elaichi works the same way behind every client: one connection, one consent screen, your own access. How Elaichi connects to AI clients covers that part — this page is the ChatGPT half.

Before you start

Requirement Detail
ChatGPT plan Business, Enterprise or Edu. MCP support is web-only today
Developer mode Must be on for your account. On Business plans only admins and owners can turn it on
Elaichi account The same sign-in you use for the web app

On Enterprise and Edu an admin can also grant developer mode through Permissions & Roles → Connected Data.

Connect ChatGPT to Elaichi

  1. In ChatGPT, open Settings → Apps and turn on developer mode.
  2. Choose Create, paste the endpoint, then run Scan tools.
  3. Sign in to Elaichi and approve what the app can do.

The developer mode toggle sits under Advanced Settings. Paste the endpoint exactly as Elaichi gives it to you. It is an OAuth endpoint, so there is no bridge command to configure, no API key to paste, and no credential anywhere in the URL. You will not be asked for a client ID or secret either — Elaichi registers ChatGPT automatically when it first makes contact.

Signing in brings up Elaichi's consent screen. Only Read is granted by default, and for most ChatGPT use you want Read and Run tools — see Approve what the client can do for what each scope covers.

Connect your first app

Start by pasting this into ChatGPT — it is the same prompt the Connect your AI client dialog hands you, and it both confirms the connection and gets you moving:

Elaichi is connected. List the Elaichi tools you have, then help me connect my first app. If a sign-in comes up, stop and tell me. I approve the access myself.

Those last two sentences are deliberate. A model cannot grant itself access to Elaichi — approving is yours to do. Without them a client will happily report success while the sign-in sits there unanswered.

Connecting the app itself happens in Elaichi, not in ChatGPT — see Connecting an account.

Anything you connect appears in ChatGPT without re-adding anything there — same endpoint, more tools behind it. The same is true in reverse: disconnect in Elaichi and it disappears from ChatGPT.

Good to know

  • ChatGPT cannot reach a local MCP server. Use the hosted endpoint, not a localhost address.
  • Write actions prompt for confirmation in ChatGPT based on your permissions — treat that as a convenience, not the security boundary. The scopes you granted are the real one.
  • To disconnect, remove the app in ChatGPT, or revoke the grant in Elaichi — revoking stops the token working immediately.

Troubleshooting

Symptom Likely cause
Scan tools finds nothing No apps connected in Elaichi yet, or no toolbox you can reach. Connect an app first
Sign-in loops or never returns Developer mode is off, or your plan does not include MCP support
A tool you expect is missing It is blocked by a restriction, or it is not in a toolbox you can reach. Connected tools are never listed, so ask ChatGPT to search for it
A call is refused after consent The scope it needs was not granted. Re-connect and widen the consent
A newly connected app does not appear Most clients cache the tool list — start a new conversation, or re-scan tools