Claude · MCP connector

Give Claude six honest tools instead of an API key.

looot runs its MCP server locally, over stdio, from your own checkout. Point Claude Desktop at it and Claude gets the same six scoped tools every other client gets: discover, inspect, run, runs_get, runs_list, balance. No secrets in the config, no hidden seventh tool. The local demo needs no account or provider key. Production connections remain fail-closed until configured and approved.

For humansFor agents

Generate your config Start your workspace

Claude Desktop, not a hosted browser connector

Claude.ai's browser-based custom connectors expect a remote HTTPS server URL. looot doesn't run one of those yet: today the MCP server is a local process, started from your checkout, speaking stdio. That's the same shape Claude Desktop's connector settings already expect, which is why Claude Desktop is the supported path right now. If you're on claude.ai in a browser with no desktop app installed, there's no looot connector for you yet, and this page won't pretend otherwise.

Config file:Claude Desktop's claude_desktop_config.json

Restart Claude Desktop after adding the block and ask Claude to list its tools. It should see exactly six, all named above. The exact command for your chosen workspace ID is generated on the setup page — reuse it there rather than copying one by hand. Full config for agents has the exact JSON body.

Six tools, no more and no fewer

Every MCP client gets the same surface. Claude doesn't get a bigger or smaller one.

discover

Search the catalog by capability, not vendor name.

inspect

Read one operation's real contract, params, and version.

run

Execute an operation. Quoted, reserved, and settled once.

runs_get

Fetch one run's status and evidence by ID.

runs_list

Page through this tenant's run history.

balance

Read remaining budget before spending it.

What Claude can actually call today

The local demo ships deterministic sample data under three capabilities: web.search, company.enrich (including an Apollo-style and a PDL-style sample), and media.generate. Ask Claude to discover by capability and it will find these, run them, and hand back raw, canonical, or field-mapped output with provenance attached. No live provider credentials are involved until you configure and approve one.

Built so Claude can't double-spend or fake a result

Effect-aware retry

An uncertain outcome doesn't get retried into a second charge. looot checks what actually happened before it tries again.

Versioned contracts

Every operation Claude calls carries a contract version, so a provider change can't silently reshape what Claude gets back.

Every call is written to a hash-chained, redacted audit log, tied to one tenant. Set up the connection first at the setup center, which lists every required account, env var, and scope without ever printing a secret.