Connect Cursor

kordi in Cursor.

Cursor's Agent speaks remote MCP. Add kordi with a token and ask about your subscriptions without leaving your editor — what to pause, what's about to charge you.

Get a token

Generate a 90-day token at kordiapp.com/token. Treat it like a password — anyone holding it can read your subscriptions.

Add kordi to Cursor

Open Cursor Settings → MCP → Add new server, or create ~/.cursor/mcp.json (global) / .cursor/mcp.json (this project) with:

{
  "mcpServers": {
    "kordi": {
      "url": "https://kordiapp.com/mcp",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

Cursor uses url for remote (Streamable HTTP) servers — no command needed. Save, then flip kordi on in the MCP settings list.

Ask away

Open the Agent (⌘I) and ask. Cursor calls kordi's tools to pull your live data.

Cursor — Agent

> what subscriptions am I paying for?
  ⚡ kordi (MCP): kordi_list_subscriptions
You're tracking 7 services — $94.43/mo. Want a rotation plan?

Simulated — real tool, real response shape.

Notes

One token, every client. The same kordi token works in any MCP client — reuse it across Cursor, the Gemini CLI, and the rest.

Keep it out of git. For a project .cursor/mcp.json, Cursor expands ${env:VAR} in headers — reference an env var ("Bearer ${env:KORDI_TOKEN}") instead of committing the raw token.

401 / unauthorized: the token is mistyped or past its 90 days. Regenerate at kordiapp.com/token and update your config.