CLAUS Builder MCP

Enter https://claus.si/Club with a CLAUS NFT and a verified linked X account.
Open https://claus.si/Build and choose MCP to create a named, revocable key.
Keys start read-only. Enable write access only if your client should create,
save or submit projects. You can restrict a key to one existing project;
a project-bound key cannot create new projects. Keys expire after 30 days.
Every request rechecks current membership, X linkage and revocation.

Streamable HTTP URL: https://claus.si/api/mcp
Authorization: Bearer <your workspace key>
Accept: application/json, text/event-stream

Initialize first, then send MCP-Protocol-Version with the negotiated version.
Supported: 2025-11-25, 2025-06-18, 2025-03-26. Responses use JSON. GET is 405;
there is no server-initiated event stream. Clients requiring OAuth discovery
can use the Node 24 stdio adapter sdk/claus-mcp.mjs instead. Supply the key in
CLAUS_BUILDER_TOKEN, never in source, prompts, command arguments or commits.

Tools: list_projects, read_project, create_project, save_project,
submit_project, export_project, list_templates, read_template.
read_project and export_project accept an optional saved revision number.
Use a stable requestId for every mutation. After an uncertain response read
the same project and reuse the exact ID and input. Do not start a new paid run.

Projects remain private to their author, even if the NFT is sold. A transferred
NFT does not reset its daily new-project allowance. Existing project reads and
exports require current Club membership. This pilot allows one new project per
member/day, one use per NFT/day, and three new projects across the service/day.
Projects retain up to 12 versions and have three offline check attempts across
their lifetime. The current shared build budget is six USDC and six checks/day;
CLAUS's own prototypes share it. Uncertain paid attempts keep their reservation.
Temporary daily exhaustion waits for the next UTC day without discarding work.

Submitting shares precisely one checked source version with CLAUS for private
Club review. It does not make the project public or install a hook. Later source
versions stay private until separately submitted. Your external coding client
can read private source and may send it to its own model provider.

JavaScript checks use a fixed offline runner, synthetic data, no dependencies,
network or wallet access. The v4 starter is for local Foundry use; Solidity is
not supported by the hosted runner yet. Passing tests is not a security audit.
No production deployment, payment, wallet or contract-administration tools are
exposed. This is a bounded application workflow, not a general inference API.

Solidity/v4: create_project accepts runtime "solidity" (default "javascript").
The choice is permanent for that project. Upload src/**/*.sol and test/**/*.sol
with at least one test/*.t.sol, plus optional README.md and module.json. Do not
upload foundry.toml, dependencies, scripts or keys. The fixed cloud worker pins
Foundry 1.8.0, solc 0.8.27 and upstream v4-core/forge-std commits. Its receipt
contains the exact source hash and toolchain; tests remain offline and synthetic.
The same project, daily compute and test limits apply to both runtimes.