Skip to main content

Connect Cursor to Floxar

Cursor's desktop application and command line share one mcp.json. Cursor publishes no metadata document, so it identifies itself with the identifier Floxar publishes for it, cursor. There is no client secret. The connection is confirmed with Cursor 3.22.12 (desktop).

Before you start, make sure MCP is on for your account and have your account URL ready. Connecting an AI client explains both, and what the sign-in and consent page show.

Add Floxar​

  1. Add the server to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (this project). If the file already lists servers, add only the Floxar entry inside the existing mcpServers object. Keep the auth block as shown: CLIENT_ID is the identifier Floxar publishes for Cursor, and scopes are what Cursor asks to be allowed.

    {
      "mcpServers": {
        "acme-floxar": {
          "url": "https://mcp.floxar.com/a/<account_id>",
          "auth": {
            "CLIENT_ID": "cursor",
            "scopes": ["floxar.read", "floxar.execute", "floxar.author", "offline_access"]
          }
        }
      }
    }

  2. Start the server in Cursor. When it asks you to sign in, sign in to Floxar in the browser window, confirm the account and allow the connection. From the command line, run agent mcp login acme-floxar.

What the sign-in looks like​

The consent page shows Cursor under Floxar's label for it, with its vendor. Cursor runs on your computer, so the connection returns to a local address, and the consent page says so.

Known limits​

  • Type the identifier exactly. A CLIENT_ID other than cursor is refused as an invalid client.
  • Disconnect in Cursor's MCP settings is local only. The connection stays active in Floxar until you or an account admin end it there (see "Disconnecting and revoking" in Connecting an AI client).
  • After a revocation, Cursor reports that the call failed on authentication and offers to authenticate again; a fresh sign-in and consent restore the connection.

Last reviewed: 2026-09-30