Put your subscriptions in the chat.

Claude Desktop

Claude Desktop's local config only launches local servers, so a remote server like kordi connects through the mcp-remote bridge — you'll need Node.js installed (check with node --version). In Claude Desktop, open Settings → Developer → Edit Config — that creates and opens claude_desktop_config.json for you — and paste:

{
  "mcpServers": {
    "kordi": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://kordiapp.com/mcp", "--header", "Authorization:${KORDI_AUTH}"],
      "env": { "KORDI_AUTH": "Bearer <your-token>" }
    }
  }
}

Replace <your-token> with your token (keep the word Bearer and the space). The ${KORDI_AUTH} env-var dance isn't decoration — it sidesteps a known argument-quoting bug in Claude Desktop on Windows, and works fine on Mac. Save, then quit Claude Desktop completely and reopen it (closing the window isn't enough). kordi appears under the tools icon in a new chat. Editing by hand instead? The file lives at ~/Library/Application Support/Claude/ on Mac, %APPDATA%\Claude\ on Windows.

Claude Code

One command in your terminal, then restart your session:

claude mcp add --transport http kordi https://kordiapp.com/mcp --header "Authorization: Bearer <your-token>"

Cursor

Cursor speaks remote MCP natively — no bridge needed. Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json inside one project, then enable it under Settings → MCP:

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

Any other MCP client

Raycast, Windsurf, custom agents — anything that supports remote MCP (Streamable HTTP): point it at https://kordiapp.com/mcp with the header Authorization: Bearer <your-token>. If your client can't send headers at all, there's a legacy fallback — append the token to the URL — but prefer the header (URLs end up in logs and history); treat this whole URL as a secret:

https://kordiapp.com/mcp?token=<your-token>