Skip to content

Cursor

Connect Cursor to Elaichi once per machine. After that, every app your organization connected in Elaichi, and every tool you are allowed to use, is available in Cursor. Cursor 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 Cursor steps.

Before you start

Requirement Detail
Cursor Any recent version with MCP support.
Where it applies Cursor reads a file on your computer, so setup is per machine, and optionally per project. Unlike Claude and ChatGPT, there is no account-level setting.
Elaichi account The same sign-in you use for the Elaichi web app.

Connect Cursor to Elaichi

These steps match Cursor 3.24 as of October 2026. Menu paths can change.

  1. In Cursor, open Customize, then MCPs.
  2. Select New MCP Server. That opens your user-level ~/.cursor/mcp.json in an editor, which applies to every project. To set it up for one project only, edit .cursor/mcp.json inside that repository instead.
  3. Add an entry named elaichi with the endpoint as its url, then save the file.
  4. Elaichi now shows under Needs Attention as Needs authentication. Select Authenticate.
  5. Elaichi's sign-in and consent screen opens in your browser and names Cursor as the app asking. Pick your organization, choose what Cursor may do, choose the tools, then select Allow.
  6. The browser shows Authorization complete. If it asks to open Cursor, select Open Cursor.

The entry is a name and a URL:

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Use the endpoint exactly as Elaichi shows it. If the file already lists other servers under mcpServers, add this entry beside them. Do not replace the block.

You will know it worked when Elaichi appears under Connected in Customize → MCPs, with its tools listed.

Info

Do not add a type field, a command, an auth block, a client ID or a secret. Cursor detects the transport from the endpoint, and Elaichi supports dynamic client registration.

On the consent screen, for most Cursor 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 Cursor. 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 Cursor. See Connect an account. Once an app is connected, it appears in Cursor with no change to mcp.json.

What to know

  • Global or per project. ~/.cursor/mcp.json applies everywhere. .cursor/mcp.json in a repository applies to that project only. Use the project file when only one codebase should reach your tools.
  • Name Elaichi in your question. Cursor's agent may answer without calling Elaichi. Say "use Elaichi to list my open GitHub issues" so it makes the call.
  • Per machine. Setting up your laptop does not set up your desktop. Repeat the steps, including the sign-in, on each machine.
  • To disconnect, remove the entry from mcp.json, 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 Cursor.

Troubleshooting

Symptom Likely cause
The server never appears after you edit the file The JSON is invalid, usually a trailing comma or a missing brace. Fix the file and save it.
No sign-in prompt appears Elaichi is still waiting for sign-in. In Customize → MCPs, select Authenticate again.
No tools appear after you sign in No app is connected in Elaichi yet, or no toolbox you can reach has tools. Connect an app first.
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 Cursor 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.