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, 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, 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?
- Check the address. It ends in
/mcp, with no slash after it. - If the server never shows up, check that the file is valid JSON.
- 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. The same address works in ChatGPT, Claude and other clients, because the server follows the open Model Context Protocol specification.
