Shodai Agreements MCP server

Shodai Agreements SDK + MCP

Shodai turns agreement definitions into machine-readable, verifiable coordination workflows for humans, products, and AI agents. Agreements carry readable terms plus participants, valid inputs, states, transitions, and history.

This repository supports builders using the TypeScript SDK, agents or tools using MCP, and the canonical Shodai Reference App built on top of the SDK.

Start Here

Hosted MCP: https://shodai.network/mcp is the Shodai Agreements execution MCP endpoint. OAuth-capable clients connect through browser sign-in and consent for testnet access. The endpoint uses Streamable HTTP, requires an environment tool argument, supports environment-scoped API keys as a fallback, and has no hosted private-key custody.

Packages and apps: @shodai-network/agreements-api-client · @shodai-network/agreements-mcp-server · agreements-api-playground · shodai-reference-app · oauth-connect-cli (shodai-oauth)

Why Builders Use Shodai Agreements

• Shared agreement state that humans, applications, and agents can inspect.
• Deterministic next actions from authored states, inputs, issuers, and transitions.
• Validation and deployment preflight before signatures.
• EIP-712 signed authorization for deployment and participant inputs.
• State and input history for receipts and monitoring.
• Less repeated contract orchestration, indexing, and participant workflow plumbing.

Choose Your Path

Both paths converge on the same agreement lifecycle. After one quickstart works, run the end-to-end workflow.

Hosted MCP Endpoint

Configure Shodai as a remote Streamable HTTP MCP server:

URL:
https://shodai.network/mcp

Required API-calling tool argument:
environment: "testnet"

Start the connection in an OAuth-capable client, then complete Shodai browser sign-in and consent. The hosted endpoint advertises the testnet authorization server, so use environment: "testnet" for this OAuth connection.

Clients without OAuth support can send Authorization: Bearer cnspk.... API keys only work in the environment where they were created; a production key can use environment: "production". Hosted MCP never receives private keys; write tools use externally signed EIP-712 permits or typed-data preparation.

An ordinary browser GET to /mcp may return 405 because the endpoint expects MCP protocol requests. MCP surfaces on docs.shodai.network are for docs and search only; https://shodai.network/mcp is the Agreements execution endpoint.

Shortened. The full README is on GitHub.