Use Lithi with Cursor

Cursor can help assess a bounded task for Lithi Compute and use the customer Work tools after you connect an approved account. Cursor retains your project context and you decide whether to submit work and accept the result.

Assess a useful piece of work

Ask Cursor to propose a repeatable task, its permitted inputs, expected output and review checks. For a small first test, use three invented records: A says “cannot sign in”, B says “invoice is wrong”, and C says “need account access”. Classify them as access or billing; the expected labels are A: access, B: billing, and C: access. Compare that proposal with doing the work in Cursor using choose work. Share only context you authorize.

Assess whether these three invented records fit a supported Compute classification operation. Keep their IDs, use the access-or-billing rubric, and return one category per ID. Show the input, output and checks first; ask before transferring data or spending.

Offloading suitable work may preserve subscription allowance for later tasks. If your comparison is direct API usage or purchased credits, evaluate equivalent costs instead. Cursor's own reasoning, review and processed tool output still consume host usage. Check Cursor's current models and pricing for your plan's terms.

Connect your approved account

First check Compute access approval. Follow Cursor's MCP documentation for the current host setup. .cursor/mcp.json is a project configuration location, not permission to change it. Use the endpoint issued for your account and a protected credential reference supported by the host. Keep secrets out of prompts, examples, command arguments and project files.

Confirm the connection authenticates the intended account with the intended scopes. A skill or a configuration file does not itself grant access, allow data transfer or approve paid work. The MCP guide describes the account and tool boundaries.

Quote and test

Verify exactly five customer Work tools are available: lithi.quote, lithi.run, lithi.batch, lithi.status and lithi.result. Quote prices a bounded request; run and batch request execution; status and result read a job's state and result metadata. Reporting and account management are separate from these tools.

Discover a supported operation and prepare the invented records in its accepted format. If the account needs credit, complete the secure browser funding step yourself and confirm the credit on the same account. Request a quote for the bounded test, then obtain the required transfer and spend approvals before submitting. Even a synthetic submission can use paid credit. Follow your first test for the wider workflow.

Check the output and recover

Use lithi.status with the existing job ID and read lithi.result when ready. It returns bounded metadata identifying authorized result files, not plaintext rows. Retrieve the files, verify their digest, and check all three IDs against the expected labels; result verification explains the checks. If a submission or read times out, inspect the same job and preserve the original intent and idempotency key. Follow its next action before considering another submission.