Connect Kilo Code

Add looot to Kilo Code as a remote MCP server.

Kilo Code is a coding agent for VS Code and a CLI. A remote server tries Streamable HTTP first and falls back to SSE.

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.

Steps

1. Open Kilo Code Settings, MCP, click Add Server and choose Remote (HTTP).
2. Enter the server URL https://api.looot.ai/mcp. Add headers only if you use a token.
3. Or edit the Kilo config file and add the entry below under the top-level mcp key.

{
  "mcp": {
    "looot": {
      "type": "remote",
      "url": "https://api.looot.ai/mcp",
      "enabled": true
    }
  }
}

The server URL is https://api.looot.ai/mcp.

Sign-in

Kilo’s MCP page documents a URL plus optional headers and does not describe a browser sign-in. If the server answers 401, put an agent token from Settings in headers as Authorization: Bearer <token>, or bridge with mcp-remote. Do not commit the token.

Check it works

Ask Kilo Code 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.

A first prompt to try

Ask looot for my balance, then search its catalog for a tool that finds a work email from a name and company domain, and show me the price before running anything.

Troubleshooting

• Server stays disabled: check "enabled": true.
• Project and global configs both exist; the project file wins for that workspace.
• Slow runs: raise timeout (milliseconds).
• Still stuck: see Troubleshooting.

What you see when you connect

If the client uses browser sign-in, it opens looot.ai and shows the consent page: which organization to bill, which scopes to grant and how long to stay connected. See The consent page.

Sources

• Using MCP in Kilo Code: kilo.ai/docs/automate/mcp/using-in-kilo-code
• Using MCP in the CLI: kilo.ai/docs/automate/mcp/using-in-cli