# Video: Connect Cursor to Your Work Apps With One URL > 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. **TL;DR** To connect Cursor to your work apps, open Customize, then MCPs, select New MCP Server, add Elaichi's one address, https://api.elaichi.ai/mcp, as a url entry, then select Authenticate and sign in. Cursor then reaches only the tools you pick. This video shows every step on the real screens, from the mcp.json entry to the audit log. [Connect Cursor to Your Work Apps With One URL](https://www.youtube.com/watch?v=EwleY4bw0HQ) This video shows how to connect Cursor to your work apps with one URL, on the real screens. You add `https://api.elaichi.ai/mcp` as an MCP server, sign in, and choose what Cursor may do. Cursor reaches only the tools you pick. ## What does the video show about how to connect Cursor to your work apps? The video follows one setup from start to finish. The written guide has the longer detail where it helps. - **0:00** Add Elaichi in Cursor's MCPs list, as a url entry in `mcp.json`. - **0:38** Select Authenticate, sign in to Elaichi, and choose what Cursor may do and which tools it can use. - **1:11** Ask Cursor for something from a connected app. - **1:26** Check the call in Elaichi's audit log. - **1:35** What to do if it will not connect. ## What do you need before you start? An Elaichi account and a recent version of Cursor with MCP support. Cursor reads MCP servers from a file on your computer, so setup is per machine ([Cursor's MCP docs](https://cursor.com/docs/mcp), checked October 2026). The steps below are from Cursor 3.24. ## How do you add Elaichi to Cursor? In Cursor, open **Customize**, then **MCPs**, and select **New MCP Server**. That opens your `mcp.json` file. Add an entry named `elaichi` with one field, `url`, set to `https://api.elaichi.ai/mcp`, and save the file. There is no type, no command and no key. Cursor's docs say a remote server is defined with a `url` field, and that it supports OAuth for servers that need it. Elaichi then shows in your MCPs list as needing authentication. Cursor registers itself with Elaichi as an OAuth client through dynamic client registration, the standard in [RFC 7591](https://www.rfc-editor.org/rfc/rfc7591), so nobody pastes a client ID or a secret. These steps are as of October 2026, and Cursor keeps moving its menus. ## What do you choose when you sign in? Select **Authenticate**. Cursor opens Elaichi's sign-in in your browser. Pick your organization, then tick what Cursor 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 Cursor everything you can use. **Only the ones I pick** limits it to the toolboxes you choose. Then select **Allow access**. The browser shows that authorization is complete and may ask to open Cursor. Select **Open Cursor**, and Elaichi is listed as connected. ## How do you check that Cursor can reach your apps? Open the agent chat and ask for something from one of your connected apps. Name Elaichi in the question, or Cursor's agent may answer without calling it. Cursor runs the call through Elaichi and answers with live data. To confirm it worked, open the audit log in Elaichi. The call is there: who made it, that it came through Cursor, and which tool it ran. In the video, a read-only request showed no approval card in Cursor, and Elaichi's audit log recorded that it needed no approval because it only read data. ## What if you cannot connect Cursor to your work apps? 1. Check the address. It ends in `/mcp`, with no slash after it. 2. If the server never shows up, check that the file is valid JSON. 3. If there is no sign-in prompt, select Authenticate again. For the full written steps, the team setup and what each developer can reach once connected, read [Connect Elaichi to Cursor for a whole team](/blog/cursor-mcp-one-endpoint-vs-per-developer/). The same address works in [ChatGPT](/blog/connect-chatgpt-to-your-work-apps/), [Claude](/blog/connect-claude-to-your-work-apps/) and other clients, because the server follows the open [Model Context Protocol specification](https://modelcontextprotocol.io/specification/2026-07-28). ## FAQ ### Where does Cursor keep the Elaichi entry? In mcp.json. The file in your home folder, ~/.cursor/mcp.json, applies in every project, and a project's .cursor/mcp.json applies to that project only. In the video, New MCP Server opens the file in your home folder. ### Do I need an OAuth client ID to connect Elaichi to Cursor? No. The entry holds only the url. Cursor registers itself with Elaichi as an OAuth client, and each person signs in with their own identity. ### Does this work with Claude, ChatGPT or another MCP client? Yes. Elaichi works with Claude, ChatGPT, Cursor 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 Cursor for a whole team](/blog/cursor-mcp-one-endpoint-vs-per-developer/) — To connect Elaichi to Cursor, add one URL to mcp.json or share it as a Team MCP server, and each developer signs in with OAuth. No API key. - [Video: Connect ChatGPT to Your Work Apps With One URL](/blog/connect-chatgpt-to-your-work-apps/) — Watch how to connect ChatGPT to your work apps with one URL: add Elaichi as a custom MCP server, choose what ChatGPT may do, and check it in the audit log. - [Video: Connect Claude to Your Work Apps With One URL](/blog/connect-claude-to-your-work-apps/) — 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.