Connect Cursor

Add the looot MCP server to Cursor, sign in with the browser or a header token, and check it works.

Cursor reaches looot’s catalog, balance and runs over MCP, through a one-click install link or a config file.

Before you start you need a looot account. The runs you make spend the organization’s balance, so top up before your first paid run. See Before your first run.

Sign in with the browser

The server URL is https://api.looot.ai/mcp. Nothing to copy: you sign in on looot.ai, pick the organization to bill and click Connect.

One-click deeplink

cursor://anysphere.cursor-deeplink/mcp/install?name=looot&config=eyJ1cmwiOiJodHRwczovL2FwaS5sb29vdC5haS9tY3AifQ==

~/.cursor/mcp.json or .cursor/mcp.json

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

Headless: a token in the header

Only for CI and machines with no browser. Create an agent token in Settings and send it as Authorization: Bearer <token>. Never commit it.

Headless: ~/.cursor/mcp.json with a header

{
  "mcpServers": {
    "looot": {
      "url": "https://api.looot.ai/mcp",
      "headers": {
        "Authorization": "Bearer <agent token from looot.ai Settings>"
      }
    }
  }
}

Notes

• Cursor opens browser sign-in the first time a looot tool is needed (Settings, MCP shows “Needs login”).
• Cursor desktop uses the callback http://localhost:8787/callback, so a looot gateway running locally on 8787 blocks sign-in.

Check it works

Ask Cursor to call balance or catalog_overview. Both are free. A working connection answers with your available balance, or the catalog’s categories and job counts.

What you see when you connect

The browser opens looot.ai and shows the consent page: which organization to bill, which scopes to grant and how long to stay connected. See The consent page.