Cursor

A JSON file, per project or per user.

Kind MCP client

Transport Remote HTTP, declared in mcp.json.

Config .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)

Setup

Create .cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project.
Add the block below.
Open Settings → MCP and check the server shows as connected with six tools.
Use it from Composer or chat in Agent mode.

{
  "mcpServers": {
    "unzoi": {
      "url": "https://api.unzoi.com/mcp",
      "headers": { "x-api-key": "nai_your_key_here" }
    }
  }
}

What differs here

The Settings → MCP panel shows the tool list it actually retrieved. If it is empty, the problem is the connection; if it lists six tools, the problem is your prompt or the mode you are in.
Tools are only called in Agent mode. In a plain chat the server is connected and never used, which reads as broken.
A project-level .cursor/mcp.json is convenient and also a file people commit. Prefer the global one for anything holding a real key.

Next

Get a key at console.unzoi.com, if you have not.
The tool reference — what the model is reading when it chooses between the six tools.
Stories for context windows — the one habit that most changes how well an agent works against this API.
Limits — an agent that loops can spend a monthly quota faster than you expect.
Cursor's own MCP documentation — authoritative for anything about the client itself, including config paths, which move.

Endpoint, for copying: https://api.unzoi.com/mcp