Connect Gemini CLI

kordi in the Gemini CLI.

The Gemini CLI speaks remote MCP. Point it at kordi with a token and ask about your subscriptions right from your terminal — set up in one command.

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 the CLI

Run one command (swap in your token). It registers kordi over Streamable HTTP with your token as a Bearer header.

zsh — gemini

$ gemini mcp add --transport http kordi https://kordiapp.com/mcp --header "Authorization: Bearer <your-token>"
✓ MCP server "kordi" added (http)

Prefer editing config directly? Add this to ~/.gemini/settings.json — use httpUrl (not url; url is for SSE):

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

Ask away

Start gemini and ask. The model calls kordi's tools to pull your live data.

zsh — gemini

> 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 the Gemini CLI, Cursor, and the rest.

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

Other clients? Cursor, Claude, Raycast, and more are on the connect page; full reference in the docs.