Setup for Claude Code

Give Claude Code six tools instead of a hundred loose ones.

looot connects to Claude Code as a single MCP server. Your agent gets discover, inspect, run, runs_get, runs_list, and balance, scoped to one tenant, backed by an audit log, with production connections fail-closed until you configure and approve them. The local demo needs no account or provider key. Setup takes about three minutes and never asks you to paste a secret into a config file.

For humansFor agents
Generate the MCP config Start your workspace

Why point Claude Code at looot

A fixed tool surface
Claude Code sees the same six MCP tools every time: discover, inspect, run, runs_get, runs_list, balance. Nothing hidden, nothing that grows without you noticing.
Tenant identity is config, not a prompt
The workspace ID your agent runs under is bound at the MCP process level. An agent can't talk itself into a different tenant mid-conversation.
No surprise charges on a bad outcome
Every run is quoted before it executes and reconciled after. If a provider call ends in an uncertain state, looot does not double-charge on retry.
Evidence, not vibes
Every run lands in a hash-chained audit log. looot never reports a call as run, verified, or connected without a receipt backing that claim.

What Claude Code actually calls

The same four-step journey every operation takes, whether it's a web search, a company enrichment lookup, or a media generation job.

1

discover

Claude Code asks what it can do. looot returns the operations available under web.search, company.enrich, and media.generate for that tenant.

2

inspect

Before running anything, the agent reads the versioned contract for an operation: required inputs, output shape, current price basis.

3

run

looot reserves against budget, executes, and settles. Failures fail closed. Nothing runs against a live provider without configuration and approval.

4

runs_get / runs_list / balance

The agent (or you) can pull a run's raw, canonical, or mapped output with field-level provenance, list history, and check remaining budget at any point.

discoverinspectrunruns_getruns_listbalance

The real setup steps live in one place

looot's setup center generates your actual MCP config from a reviewed checkout: pick a tenant workspace ID, copy one command, restart Claude Code, and confirm it lists exactly six looot tools. No steps are duplicated here so there's only one place that can drift out of date.

Open the setup center