Cursor + looot
Give Cursor's agent a defined set of tools, not raw API keys.
looot exposes six MCP tools to Cursor: discover, inspect, run, runs_get, runs_list, and balance. Cursor's agent finds what it can call, reads the contract, and runs it, all inside your organization's budget with an audit trail on every call.
Your workspace needs no account or provider key to start. Production connections remain fail-closed until configured and approved.
MCP tools
What Cursor sees
discover
List the operations your organization is allowed to reach.
inspect
Read an operation's contract before calling it: inputs, price basis, output shape.
run
Execute a versioned operation contract with quote-before-run pricing.
runs_get
Fetch the full record for one run, including its evidence.
runs_list
Page through recent runs for the organization, cursor-paginated.
balance
Check remaining budget before the agent spends it.
Connect Cursor in four steps
The setup center in your workspace has the exact connection string and scopes for your organization. These steps are the shape of the flow, not a substitute for it.
Create a workspace
Start in your workspace, no account or provider key needed, or set up a real organization when you're ready.
Open the setup center
Every required account, environment variable, and scope is listed there. Nothing is ever printed once it's a secret.
Point Cursor at the MCP server
Add the gateway as an MCP server in Cursor's settings using the connection details from your workspace.
Let the agent discover and run
Cursor's agent calls discover and inspect on its own, then run for anything it needs, all inside your organization's budget.
Organization isolation
Every discover, inspect, and run call is scoped to your organization. Cursor never sees another workspace's tools or data.
Quote before run
Each operation has a versioned price basis. The agent gets a quote before it spends, and an uncertain outcome never gets charged twice.
Honest evidence
runs_get and runs_list return a hash-chained audit log. looot never marks a run tested, verified, or connected without a real receipt behind it.
Try it in your workspace first.
No account, no provider key. See exactly what Cursor would call before pointing it at anything real.