MCP SERVER · OFFICIAL PROJECTAuthor a machine-readable agreement, preflight it, sign it with EIP-712, and drive its lifecycle on-chain.
LABSCO SUMMARY
The write tools hold no key — they build the exact typed-data payload for your own wallet to sign, then submit the signature components. With validate and preflight sitting in front of that, the order of operations is arranged so nothing irreversible happens on a guess.
The MCP surface for Shodai Agreements. An agreement carries readable terms plus participants, valid inputs, states and transitions; these tools validate the authored JSON, check it is deployable, build the exact EIP-712 payload to sign, deploy it, then submit signed inputs that advance it.
The hosted endpoint is https://shodai.network/mcp over Streamable HTTP. OAuth-capable clients sign in through the browser; others send an Authorization: Bearer key. Every API-calling tool takes an environment argument, and a key only works in the environment it was created in — the hosted OAuth connection advertises testnet. There is no hosted private-key custody: writes go through externally signed EIP-712 permits, or through the typed-data preparation tools. A local package, @shodai-network/agreements-mcp-server, mirrors the same surface. Keys come from the developer portal.
One command plus a key — npx -y @shodai-network/agreements-mcp-server, then supply credentials
USE CASES
Validate the JSON on its own, then preflight it against the chain, values and participant wallets.
Get the typed data, sign it wherever your key lives, and submit the signature to deploy.
Build the payload for the input you are allowed to submit, sign it, and move the state forward.
Read the current state, and check whether the input is pending, mined or failed.
The full record with its participants and deployment address, plus the rendered prose document.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
deploy_agreementDeploys authored agreement JSON using an EIP-712 permit; the API submits the on-chain transaction and returns the deployed agreement record. Provide a pre-signed permit (signer, deadline, signature), or call prepare_deployment_typed_data first to obtain the payload to sign. Always run preflight_deployment before deploying. Requires the agreements.write scope.
get_agreementReturns a single agreement record, including the full authored agreement JSON and hosted record context (participants, observers, owner, deployment address).
get_agreement_documentReturns the rendered hosted prose document for an agreement by documentId, including content type, display name, chain, docUri, and agreement record references. Use documentId from list_agreements/get_agreement or from prepare_deployment_typed_data.
get_agreement_stateReturns the current state of an agreement. For deployed agreements, interpret the state against the states defined in the authored agreement lifecycle (execution.states). Use this to poll for transitions after submitting an input.
get_input_historyReturns recorded input submissions for an agreement, with pagination and filtering. Use this to inspect which events have been submitted and whether each is PENDING, MINED, or FAILED.
list_agreementsLists agreement summaries visible to the current API key. Supports pagination (cursor + limit), filtering by chain and state, and sorting. Returns summaries only; use get_agreement for the full record.
preflight_deploymentChecks whether authored agreement JSON plus target chain, deployment values, participant wallet mappings, and observer context are ready for deployment. This does not deploy the agreement and does not require a signature. Always run this before signing a deploy permit. Requires the agreements.write scope.
prepare_deployment_typed_dataBuilds the exact EIP-712 payload that must be signed to authorize deployment of the given agreement JSON. Sign the returned typedData with the deploying wallet (eth_signTypedData_v4 / viem signTypedData), then call deploy_agreement with signer, deadline, and the signature components. No transaction is sent and nothing is stored. Reads the signer nonce from the target chain.
prepare_input_typed_dataBuilds the exact EIP-712 payload that must be signed to authorize submitting an input to a deployed agreement. Sign the returned typedData with a wallet allowed by the input definition, then call submit_input with signer, deadline, and the signature components. No transaction is sent and nothing is stored. Reads the agreement record and signer nonce.
submit_inputSubmits a signed input to a deployed agreement, advancing its on-chain lifecycle. The input ID and values must match an input defined by the agreement JSON, and the signer must be allowed by that input. Provide a pre-signed permit (signer, deadline, signature), or call prepare_input_typed_data first. Requires the agreements.write scope.
validate_agreementChecks only the authored agreement JSON document and returns participant variable keys, input IDs, state IDs, and warnings. This does not validate deployment values, participant wallet addresses, signer, or permit data — use preflight_deployment for that. Iterate on the agreement JSON until this returns no blocking warnings. Requires the agreements.write scope.
BEFORE YOU INSTALL
11 tools when we connected. On the hosted endpoint every API-calling tool takes an environment argument, testnet or production; the local stdio server reads it from an environment variable instead.
CONTEXT COST
Rated by the size of the 11 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"shodai-agreements": {
"command": "npx",
"args": [
"-y",
"@shodai-network/agreements-mcp-server"
],
"env": {
"AGREEMENTS_API_KEY": "<YOUR_AGREEMENTS_API_KEY>",
"AGREEMENTS_API_ENVIRONMENT": "testnet"
}
}
}
}npx -y @shodai-network/agreements-mcp-serverhttps://shodai.network/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP servers
Kevthetech143
nirholas
ChainBench
Bortlesboat