Connect your agent

Add the looot MCP server to any agent client, sign in with the browser or a header token, and see what the consent page shows.

Agents reach looot over MCP (Streamable HTTP) at one URL:

https://api.looot.ai/mcp

The agent gets the same catalog, balance and runs as the CLI. There are two ways to sign in.

• Browser sign-in (the default). Add the URL to your client and start its sign-in. A browser opens on looot.ai, you pick the organization and click Connect. The client keeps its own token and renews it while you’re connected. You never see or copy a key.
• A token in the header (the fallback). Send Authorization: Bearer <token> with every request. Use it for CI, scripts, and clients that can’t open a browser. The token comes from Settings, Agent tokens, on looot.ai. See Headless: CI and scripts.

Both ways give the agent a normal looot token, scoped to what you chose, billed to one organization, listed in Settings, Agent tokens, and revocable there.

Before the first paid run, top up the organization’s balance. See Before your first run.

Pick your client

Claude CodeTested

Tested by hand. Add the server and sign in from your shell.

claude.ai

Custom connector, browser sign-in only.

Claude Desktop

Same custom connector as claude.ai.

ChatGPT

Developer mode connector, browser sign-in only.

Codex

CLI and app, both ways supported.

Cursor

One-click install or a config file.

VS Code

GitHub Copilot agent mode.

Gemini CLI

Config file plus an in-CLI auth command.

Windsurf

Config file; browser sign-in not confirmed.

Devin

Custom MCP in Customize, browser sign-in.

Cline

VS Code extension. Token in its MCP settings file.

OpenClaw

One command to add, one to sign in with the browser.

Hermes Agent

YAML config plus a browser sign-in command.

Grok

Connectors page, admin flow, and the CLI and API paths.

Copilot Studio

MCP onboarding wizard inside an agent's Tools.

Muse

Custom connector by prompt; not tested.

Lovable

Connectors, custom MCP server, OAuth by default.

Bolt

Connectors page, custom MCP server, MCP OAuth.

v0

Prompt form, MCPs menu, manual server with OAuth.

Base44

Account preferences, custom MCP, OAuth or a header token.

Replit

Integrations pane install link with OAuth.

LibreChat

A librechat.yaml entry; LibreChat handles OAuth per user.

Open WebUI

Admin integrations, MCP Streamable HTTP, OAuth 2.1.

Gumloop

Settings, Connectors, Add MCP Connector with a public URL.

Retool

Agent tool, MCP resource, OAuth 2.0 with PKCE.

Zed

A context_servers entry with just the URL; Zed runs OAuth.

Continue

A .continue/mcpServers YAML file, agent mode.

Kilo Code

Settings, MCP, Add Server, Remote (HTTP).

Roo Code

mcp_settings.json with a token header; no browser sign-in yet.

Warp

A URL server in settings; Warp runs OAuth.

JetBrains AI Assistant

Settings, Tools, AI Assistant, MCP, a JSON entry with the URL.

mcp-remote

Bridge for stdio-only clients.

Other pages: Headless: CI and scripts, looot init, Troubleshooting.

Other MCP clients

Any client that takes a remote MCP URL can reach looot. These have a page each, none tested by hand; use the URL above, or the mcp-remote bridge for a client that only runs local servers.

Perplexity

Account settings, Connectors, a custom remote connector with OAuth.

Le Chat

Custom MCP connector tab, OAuth 2.1 detected automatically.

Goose

Settings, Extensions, a remote Streamable HTTP extension.

Client names and logos are trademarks of their owners. They are shown here only to say which clients looot works with; it doesn’t mean those companies endorse looot.

Which clients are tested

“Tested” means someone clicked through the client’s own sign-in by hand and checked the tools loaded. Everything else is “not tested by hand yet”: the install steps follow the client’s own docs, but nobody has verified them end to end.

The consent page

The client opens looot.ai/oauth/consent. If you’re signed out, looot.ai asks you to sign in first and brings you back to the same request. The page is titled Connect an app and shows:

• Connect app name to looot? The name the client registered with. If the client registered itself, the page says looot did not verify who is behind it. A client that publishes a signed client document, such as Claude Code, shows as verified.
• Credentials will be sent to, the address the client gets the result on. For an app on your own computer that’s localhost or 127.0.0.1 with a port, and the page adds a warning to click Cancel if you didn’t just start that connection. For a hosted client it’s that client’s own site, such as claude.ai or chatgpt.com.
• Signed in as, your email.
• Organization, with its balance. Calls made through this connection spend this organization’s balance. If you belong to more than one, pick another one here.
• Scopes, checkboxes for what the agent may do. Only scopes your account can grant are listed. catalog.read, runs.read, runs.execute and usage.read are ticked by default, which is what an agent needs to search, run and check the balance. See the scope table below.
• Stay connected for, a duration you pick, with 30 days as the default.
• Connect and Cancel.

Only an owner or admin of the organization can click Connect.

After Connect, the browser goes back to the client, and the client finishes on its own. If the browser doesn’t switch back, the page shows a “return to app name” link.

What happens next:

• The client holds an access token and renews it in the background until the duration you picked runs out. Then it asks you to sign in again.
• The token appears in Settings, Agent tokens, as “app name (connected)”, for example “Claude Code (connected)”.
• Revoke it there any time. The client’s next call gets a 401 and its next renewal fails, so it asks you to sign in again.

Cancel sends the client an access_denied answer. Nothing is created.

Token scopes

Set up any client with one paste

Some agents can read a URL and configure themselves. Paste this into the chat:

Set up looot: read https://api.looot.ai/llms.txt and follow it.