Shodai Agreements

Name: Shodai Agreements
Author: CNSLabs

@CNSLabs

Repository

About Shodai Agreements

A client library for the agreement API

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "shodai-agreements": {
      "type": "streamable-http",
      "url": "https://shodai.network/mcp",
      "headers": {
        "Authorization": "Bearer ${SHODAI_API_KEY}"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Shodai Agreements?

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. The MCP server provides hosted Streamable HTTP or local stdio access for agents and MCP‑capable clients.

How to use Shodai Agreements?

Configure the hosted MCP endpoint at https://shodai.network/mcp with bearer API‑key auth, or run the local stdio MCP server with npx -y @shodai-network/agreements-mcp-server. Use tools like validate_agreement, preflight_deployment, deploy_agreement, submit_input, and resources/prompts for agreement lifecycle operations.

Key features of Shodai Agreements

Shared agreement state inspectable by humans, apps, and agents.
Deterministic next actions from authored states 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 and participant workflow plumbing.

Use cases of Shodai Agreements

An agent validates an agreement structure before deploying it to testnet.
A TypeScript application uses the SDK to deploy agreements with signed permits.
A multi‑party workflow reads current state and submits signed inputs.
A monitoring service inspects input history and agreement lifecycle events.
A developer preflights deployment and runs end‑to‑end workflow examples.

FAQ from Shodai Agreements

What does Shodai Agreements do that alternatives do not?

It provides a portable, version‑controlled definition of an agreement that humans, apps, and AI agents can all inspect and coordinate with, with deterministic transitions and signed authorization.

What are the runtime requirements for using it?

For the hosted MCP, only an API key. For local MCP, Node.js and an API key. The TypeScript SDK requires Node.js and optionally viem for permit‑signing helpers.

Where does agreement data live?

Agreements are stored on Shodai’s API servers, environment‑scoped. The hosted MCP never holds private keys; authorization uses externally signed EIP‑712 permits.

What transports and authentication are supported?

Hosted MCP uses Streamable HTTP with bearer API‑key auth. Local MCP uses stdio. API keys are environment‑scoped (testnet or production). OAuth/session auth and x402 payments are not current setup paths.

What are the known limits of Shodai Agreements?

Shodai agreements do not claim legal finality or fully autonomous enforcement. Shodai does not move value without authorized signed inputs. Hosted MCP does not hold private keys.