Skip to content

Claude

Connect Claude 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 Claude 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 Claude half.

Before you start

Requirement Detail
Claude plan Custom connectors work on Free, Pro, Max, Team and Enterprise. Free is limited to one custom connector
Who can add it On Team and Enterprise, only an Owner can add a connector. Everyone else connects to it individually once it exists
Elaichi account The same sign-in you use for the web app

Connect Claude to Elaichi

  1. In Claude, open Settings → Connectors.
  2. Choose Add custom connector and paste the endpoint.
  3. Sign in to Elaichi and approve what the connector can do.

Paste the endpoint exactly as Elaichi gives it to you. Leave OAuth Client ID and Client Secret empty under Advanced settings — Elaichi supports dynamic client registration, so Claude registers itself on first contact.

Info

Claude reaches your endpoint from Anthropic's cloud, not from your computer. The endpoint has to be reachable on the public internet — a localhost address will not work.

Signing in brings up Elaichi's consent screen. Only Read is granted by default, and for most Claude 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 Claude — 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 Claude — see Connecting an account.

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

Good to know

  • On Team and Enterprise the connector is added once, by an Owner. Everyone else then enables it for themselves and signs in as themselves — so each person's tools still follow their own access.
  • To disconnect, remove the connector in Claude, or revoke the grant in Elaichi — revoking stops the token working immediately.

Troubleshooting

Symptom Likely cause
No tools appear after connecting No apps connected in Elaichi yet, or no toolbox you can reach. Connect an app first
Add custom connector is missing On Team or Enterprise only an Owner can add one. Ask an Owner to add it, then enable it for yourself
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 Claude 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 reconnect the connector