Skip to content

MCP: Connect TofuPilot to Claude, Cursor

June 12, 2026

TofuPilot MCP server connecting Claude, Cursor, and other AI clients to test data

TofuPilot now has an MCP server. Connect Claude, Cursor, or any Model Context Protocol client to your test data and it can read your runs, phases, measurements, logs, units, parts, batches, procedures, stations, deployments, and organization members. With write access, agents can also create, update, and delete runs, units, parts, batches, procedures, and stations, including revisions and versions.

No API key to copy or rotate. You authorize once in your browser.

Connect

Your organization settings have a dedicated MCP page with copy-ready snippets for each client. Grab the one you need, authorize in the browser that opens, pick an organization, approve. A token is issued to the client. That's it.

Claude: claude mcp add --transport http tofupilot https://www.tofupilot.app/mcp, then run /mcp to authorize.

Cursor: add the URL to .cursor/mcp.json. It opens the browser on first use.

Any other client: use the endpoint with Streamable HTTP. The client discovers the OAuth flow from the URL.

Read

Every connection can read: runs, phases, measurements, logs, units, parts, batches, procedures, stations, deployments, and organization members. Same filters the API exposes. Ask for the failing units on FVT-001 this week, the out-of-limit measurements in a run, or the log lines around a failed phase, and the data comes back.

Write

Write is opt-in. When you connect a client, you choose read-only or read and write. With write, the connection can create and update runs, units, parts, batches, procedures, and stations (including revisions and versions). Deletes are there too, behind an explicit confirmation, because a delete can cascade and there's no undo.

A read-only connection can never write.

Access stays scoped

Every request runs against your organization only, enforced at the database. The connection acts with your role: operators get no access, viewers stay read-only, the rest read and write. Member emails are never exposed.

The same settings page lists every connected client, with its organization and access level, and lets you revoke any of them in one click. Revoking cuts it off immediately.

What's next

Procedure-level scoping (limiting a connection to specific procedures) is on the list. If your agent needs data the server doesn't expose yet, tell us on Discord.

See what's new in action