Claude
Connect Claude to Elaichi once. After that, every app your organization connected in Elaichi, and every tool you are allowed to use, is available in a Claude conversation. Claude is one example of an AI client. Other clients use the same Elaichi endpoint.
Where to find the endpoint: in the Elaichi web app, choose Connect in the sidebar, then copy the endpoint shown in Connect your AI client.
How Elaichi connects to AI clients explains the parts that are the same for every client: one connection, one consent screen and your own access. This page covers only the Claude steps.
Before you start
| Requirement | Detail |
|---|---|
| Claude plan | Custom connectors work on Free, Pro, Max, Team and Enterprise. Free allows one custom connector. |
| Who can add the connector | On Team and Enterprise, only an Owner can add a connector. Everyone else connects to it once it exists. |
| Elaichi account | The same sign-in you use for the Elaichi web app. |
Connect Claude to Elaichi
- In Claude, open Customize → Connectors.
- Choose Add custom connector and paste the endpoint.
- Sign in to Elaichi and approve what the connector can do.
Paste the endpoint exactly as Elaichi shows it. Leave OAuth Client ID and Client Secret empty under Advanced settings. Elaichi supports dynamic client registration, so Claude registers itself the first time it connects.
You will know it worked when Claude lists Elaichi under your connectors and shows its tools in a conversation.
Claude reaches the endpoint from Anthropic's cloud, not from your computer. The endpoint must be reachable on the public internet. A localhost address does not work.
Signing in opens the Elaichi consent screen. For most Claude use, keep See your organization and Use your connected apps ticked. Approve what the client can do explains each scope.
Connect your first app
Paste this prompt into Claude. It is the same prompt the Connect your AI client dialog gives you. It confirms the connection and helps you connect an app.
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.
The last two sentences matter. A model cannot grant itself access to Elaichi, so you must approve each sign-in yourself. Without those sentences, a client can report success while a sign-in waits unanswered.
You connect the app itself in Elaichi, not in Claude. See Connect an account. Once an app is connected, it appears in Claude with no change on the Claude side.
What to know
- On Team and Enterprise, an Owner adds the connector once. Everyone else then turns it on for themselves and signs in as themselves, so each person's tools follow their own access.
- To disconnect, remove the connector in Claude, or revoke the grant in Settings → Connected apps in Elaichi. Revoking stops the token working immediately.
- If you disconnect an app in Elaichi, it also disappears from Claude.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| No tools appear after connecting | No app is connected in Elaichi yet, or no toolbox you can reach has tools. Connect an app first. |
| Add custom connector is missing | On Team and Enterprise, only an Owner can add one. Ask an Owner to add it, then turn it on for yourself. |
| A tool you expect is missing | A restriction blocks it, or it is not in a toolbox you can reach. Connected tools are never listed, so ask Claude to search for the tool by name. |
| A call is refused after consent | You did not grant the scope the call needs. Connect again and tick that scope. |
| A newly connected app does not appear | Many clients cache the tool list. Start a new conversation, or reconnect the connector. |