# Video: Connect Claude to Your Work Apps With One URL

> Watch how to connect Claude to your work apps with one URL: add Elaichi as a custom connector, choose what Claude may do, and check it in the audit log.

**TL;DR** To connect Claude to your work apps, add Elaichi's one address, https://api.elaichi.ai/mcp, as a custom connector, sign in, and choose what Claude may do. Claude then reaches only the tools you pick. This video shows every step on the real screens, from adding the connector to the audit log.

[Connect Claude to Your Work Apps With One URL](https://www.youtube.com/watch?v=SSTSkTAp3Pg)

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](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp), 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](https://claude.com/docs/connectors/custom/add-unlisted), checked October 2026). 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 uses a client ID metadata document only when the authorization server's metadata advertises both `client_id_metadata_document_supported: true` and "none" among its token endpoint auth methods, and that it falls back to dynamic client registration if either is missing ([how Claude authenticates connectors](https://claude.com/docs/connectors/building/authentication), checked October 2026). Elaichi does not advertise client ID metadata document support, and it accepts registration under [RFC 7591](https://www.rfc-editor.org/rfc/rfc7591), so Claude registers itself dynamically.

## 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: use your connected apps, see your organization, make changes, and delete things. Delete things 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. With **Use your connected apps** ticked, a **Toolboxes** row opens a sheet on the same page. **Everything I can use** gives Claude everything you can use. **Only the ones I pick** limits it to the toolboxes you choose. Then select **Allow**. Back in Claude, Elaichi is connected, and for each tool you can choose Always allow, Needs approval or Blocked.

## How do you set up Claude for the whole company?

The work splits in two. An Owner decides once that Claude may reach Elaichi at all. Each person then signs in as themselves, and Elaichi decides what their own calls may do.

On Claude Team and Enterprise plans, an Owner or Primary Owner adds the custom connector from Organization settings, then Connectors, by clicking Add, hovering over Custom and choosing Web ([Anthropic's guide to custom connectors](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp), checked October 2026). A member without one of those roles cannot add it and has to ask an Owner ([Anthropic's connector docs](https://claude.com/docs/connectors/custom/add-unlisted), checked October 2026). On Claude Enterprise, a member whose custom role includes Manage access to Libraries can also add one ([Anthropic's guide to custom connectors](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp), checked October 2026).

Adding it for the organization gives nobody access yet. Each member finds it under Customize, then Connectors, usually marked Custom, and clicks Connect to authenticate ([Anthropic's guide to custom connectors](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp), checked October 2026). That is the sign-in and consent screen described above, and each person goes through it with their own Elaichi account. One grant per person, approved by that person.

That is the point of the split. Every tool call Claude makes runs as the person whose grant it used, with that person's permissions looked up on each request. Two people with the same connector in the same Claude organization reach different tools, because they are different people in Elaichi.

So the company-wide part is not the connector. It is the rules behind it. In Elaichi, a restriction names a role or one member and lists the connectors and tools they may reach. Every connected-tool call passes that check, whichever client sent it, so a rule on the Member role governs that person's calls from Claude without anyone touching Claude. A restriction cannot target a team or the whole organization, so write it on the role people hold, or on each member. For a worked example of one app rolled out this way, see [how a company puts Slack behind per-person connections and per-role tool rules](/blog/connect-slack-to-claude-for-the-whole-company/). Another walks through [a project tool where each person sees only their own projects and every tool that deletes is blocked](/blog/connect-asana-to-claude-for-project-teams/).

Two things decide how the first rule behaves. An allow rule turns on an allowlist for its target just by existing, so once a role carries one, every connector it does not name is blocked for that role. And a role, team or restriction change takes effect within about two minutes, not on the next call.

Claude has its own controls on top. Owners on Team and Enterprise set each connector's tools to Always allow, Needs approval or Blocked, for the whole organization, and individual users cannot override them ([Anthropic's connectors article](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities), checked October 2026). Those settings and Elaichi's restrictions are separate layers. Claude's settings decide when Claude asks before calling; Elaichi's restrictions decide what may run at all.

The audit log is the one place both ends meet. Every connected-tool call that reaches execution is written there with the person, the connector, the connection and the MCP client, so a call from Claude is recorded as a call from Claude. Anyone can read their own activity. Reading the whole organization's needs the audit permission, which the Org Owner, Org Admin and Auditor roles hold. Auditor is a free, read-only seat, so a compliance reviewer can watch the rollout without adding a billable seat.

Offboarding is the last piece. Removing or suspending a member revokes their grants in that organization, and their Claude connection stops working on the next call rather than at the end of the token's hour.

## 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?

1. Check the address. It ends in `/mcp`, with no slash after it.
2. If sign-in times out, start again from Claude and select **Connect** again.
3. If Claude says a permission is missing, reconnect and tick it.

For the full written steps on every plan, read [Connect Elaichi to Claude](/blog/connect-elaichi-to-claude/). To roll the same setup out to a whole team, read [Connect company apps to Claude and ChatGPT](/blog/connect-company-apps-to-claude-and-chatgpt/). To decide who gets which tools before anyone connects, read [Give each team only the tools it needs](/blog/give-each-team-only-the-tools-it-needs/). The connector follows the open [Model Context Protocol specification](https://modelcontextprotocol.io/specification/2026-07-28), so the same address works in other clients too.

## FAQ

### Which Claude plans can connect to Elaichi?

Free, Pro, Max, Team and Enterprise can all add a custom connector, in Claude on the web, Claude Desktop and Cowork. Free is limited to one custom connector. On Team and Enterprise, an Owner or Primary Owner adds it for the organization, and members then connect it themselves.

### Do I need an OAuth client ID to connect Elaichi to Claude?

No. Leave the advanced settings empty. Claude uses a client ID metadata document only when the authorization server advertises support for it, and otherwise registers through dynamic client registration. Elaichi does not advertise metadata-document support and accepts dynamic client registration, so Claude registers itself and each person signs in with their own identity.

### Does one person's setup give the whole company access?

No. On Claude Team and Enterprise, an Owner adds the custom connector once for the organization, but that gives nobody access by itself. Each person still connects it from Customize and signs in to Elaichi with their own account. Every tool call runs as that person, with their own permissions and restrictions.

### Does this work with ChatGPT, Cursor or another MCP client?

Yes. Elaichi works with Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client. They all use the same Elaichi address, so the rules you set apply the same way in each of them.

## Read next

- [Connect Elaichi to Claude](/blog/connect-elaichi-to-claude/) — To connect Elaichi to Claude, add one URL as a custom connector and sign in with OAuth. On Team and Enterprise, an Owner adds it once for everyone.
- [Video: Connect Cursor to Your Work Apps With One URL](/blog/connect-cursor-to-your-work-apps/) — Watch how to connect Cursor to your work apps with one URL: add Elaichi in Cursor's MCPs list, choose what Cursor may do, and check it in the audit log.
- [Connect company apps to Claude and ChatGPT](/blog/connect-company-apps-to-claude-and-chatgpt/) — To connect company apps to Claude and ChatGPT, connect each account once in Elaichi, share it, and add one URL to both. No MCP server to run.
