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 cns_pk_.... 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.

• MCP quickstart: docs.shodai.network/sdks/quickstart-with-mcp
• MCP package docs: packages/agreements-mcp-server/README.md
• Execution server card: shodai.network/.well-known/mcp/server-card.json
• MCP catalog: shodai.network/.well-known/mcp/catalog.json

What This Repository Contains

Install the TypeScript SDK

Most TypeScript consumers should install the published npm package rather than this monorepo:

npm install @shodai-network/agreements-api-client

Add viem if you want the built-in permit-signing helpers for deploy and input submission:

npm install @shodai-network/agreements-api-client viem

Create a client with a named Shodai environment:

const client = new ApiClient({
  environment: 'testnet',
  apiKey: process.env.AGREEMENTS_API_KEY,
});

SDK usage and API lifecycle docs live in packages/agreements-api-client/README.md. For constructor options, methods, signing helpers, diagnostics, and exports, see the TypeScript client reference.

Run MCP Locally

Use the published MCP package for local stdio clients:

{
  "mcpServers": {
    "shodai-agreements": {
      "command": "npx",
      "args": ["-y", "@shodai-network/agreements-mcp-server"],
      "env": {
        "AGREEMENTS_API_KEY": "YOUR_API_KEY",
        "AGREEMENTS_API_ENVIRONMENT": "testnet"
      }
    }
  }
}

Local stdio mode uses AGREEMENTS_API_ENVIRONMENT; hosted MCP uses the environment tool argument. See packages/agreements-mcp-server/README.md for self-hosting, environment variables, tools, resources, prompts, and Inspector usage.

Agreement Lifecycle

For a guided run through validation, deployment, signed input submission, state reads, and input history, use the end-to-end workflow.

Agreements API Environments

The SDK prefers a named environment instead of a raw host:

const client = new ApiClient({
  environment: 'testnet',
  apiKey: process.env.AGREEMENTS_API_KEY,
});

Built-in mappings:

• testnet -> https://test-api.shodai.network
• production -> https://api.shodai.network

API keys are environment-scoped. Use a testnet key with testnet and a production key with production.

The client still supports baseUrl as an advanced override for local proxies, internal gateways, or non-standard deployments. It continues to add /v0/* automatically.

Local Development

# from the repository root
pnpm install
pnpm build
pnpm dev

The default dev command starts the Shodai Reference App. Its backend defaults to http://localhost:4199 and its frontend defaults to http://localhost:5184/agreements/.

Stop the reference app dev stack with:

pnpm dev:stop

See apps/shodai-reference-app/README.md for the required local environment files.

Run the API playground explicitly with:

pnpm dev:playground

The playground defaults to http://localhost:5176. If that port is already in use, start the playground on another port:

pnpm --filter agreements-api-playground exec vite --host 127.0.0.1 --port 4176

For local browser development, the playground is environment-first and defaults to testnet. Use the in-app environment selector to switch between hosted testnet and production API targets.

Optional package-specific validation commands:

pnpm --filter @shodai-network/agreements-api-client run lint
pnpm --filter @shodai-network/agreements-mcp-server test