This video shows how to connect Claude to your work apps with one URL, on the real screens. You add https://api.elaichi.ai/mcp as a custom connector, sign in, and choose what Claude may do. Claude reaches only the tools you pick.
What does the video show about how to connect Claude to your work apps?
The video follows one setup from start to finish. Each step below links to the longer written guide where it helps.
- 0:00 Add Elaichi as a custom connector in Claude.
- 0:33 Sign in, choose what Claude may do, and pick the tools. Then set each tool to Always allow, Needs approval or Blocked.
- 1:10 Ask Claude for something from a connected app, then check the call in Elaichi's audit log.
- 1:32 How it works on Team and Enterprise, where an owner adds the connector once.
- 1:48 Three fixes if it will not connect.
What do you need before you start?
An Elaichi account and a Claude plan that allows custom connectors. Anthropic lists custom connectors on Free, Pro, Max, Team and Enterprise, and limits Free to one (Anthropic's guide to custom connectors, checked October 2026).
On Team and Enterprise, an Owner adds custom connectors for the whole organization, under Organization settings, then Connectors (Anthropic's connector docs). Everyone else connects it from Customize once it exists. If you are not an Owner, ask one to add it first.
How do you add Elaichi as a custom connector?
In Claude, open Customize, then Connectors, and choose Add custom connector. Name it Elaichi and paste https://api.elaichi.ai/mcp, with no slash at the end. Claude checks the server and finds the sign-in settings by itself, so leave the advanced settings empty and select Add.
The advanced settings take an OAuth client ID and secret, and Elaichi needs neither. Anthropic's authentication docs say Claude falls back to dynamic client registration when a server publishes no client ID metadata document (how Claude authenticates connectors). Elaichi supports registration under RFC 7591, so Claude registers itself.
What do you choose when you sign in?
Select Connect. Claude opens Elaichi's sign-in. Pick your organization, then tick what Claude may do: read, create and change, run your tools, and delete. Delete is never ticked for you and it covers only Elaichi's own deletes, so tick it only if the person needs it.
Next, choose the tools. All my tools gives Claude everything you can use. Only the ones I pick limits it to the toolboxes you choose. Then select Allow access. Back in Claude, Elaichi is connected, and for each tool you can choose Always allow, Needs approval or Blocked.
How do you check that Claude can reach your apps?
Ask Claude for something from one of your connected apps. Claude asks before it runs a tool that needs approval, and then answers with live data pulled through Elaichi. To confirm it worked, open the audit log in Elaichi. The call is there: who made it, that it came through Claude, and which tool it ran.
What if you cannot connect Claude to your work apps?
- Check the address. It ends in
/mcp, with no slash after it. - If sign-in times out, start again from Claude and select Connect again.
- If Claude says a permission is missing, reconnect and tick it.
For the full written steps on every plan, read Connect Elaichi to Claude. To roll the same setup out to a whole team, read Connect company apps to Claude and ChatGPT. The connector follows the open Model Context Protocol specification, so the same address works in other clients too.
