Connect a stdio-only client (mcp-remote)

Bridge looot's remote MCP server into a client that only speaks stdio, with the mcp-remote package.

Some MCP clients only launch a local process over stdio and can’t call a remote HTTP server directly. The mcp-remote package bridges the two: it runs the browser sign-in on your machine and speaks stdio to the client.

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.

mcpServers entry

{
  "mcpServers": {
    "looot": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@0.14.3",
        "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: pass the header through the bridge

{
  "mcpServers": {
    "looot": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@0.14.3",
        "https://api.looot.ai/mcp",
        "--header",
        "Authorization: Bearer <agent token from looot.ai Settings>"
      ]
    }
  }
}

Notes

• mcp-remote runs the browser sign-in locally and speaks stdio to the client. The version is pinned on purpose.

Check it works

Ask the agent 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 bridge opens looot.ai in your browser and shows the consent page: which organization to bill, which scopes to grant and how long to stay connected. See The consent page.