Skip to content
MCP server

Shodai Agreements

MCP server for authoring, validating and deploying Shodai on-chain agreements

Install

Shodai Agreements is an MCP server for smart contract security. It runs as a hosted remote server, so there is nothing to install locally.

Platforms
API, CLI, Self-hosted
Runs
Remotely
Version
0.1.0
Listing updated

Similar MCP servers

Install

Run in a terminal

claude mcp add --transport http agreements https://shodai.network/mcp

Add to Settings → Connectors → Add custom connector

https://shodai.network/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "agreements": {
      "url": "https://shodai.network/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "agreements": {
      "type": "http",
      "url": "https://shodai.network/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "agreements": {
      "serverUrl": "https://shodai.network/mcp"
    }
  }
}

Add to Grok Bot desktop app → Connect apps → Add a custom connector

https://shodai.network/mcp

Enter a Name (for example "Shodai Agreements"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.

Full Grok Bot setup guide

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "agreements": {
      "type": "http",
      "url": "https://shodai.network/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

About Shodai Agreements

The README describes this server as a thin Model Context Protocol layer over the public Agreements API. It exposes the full agreement lifecycle (drafting, validation, preflight checks, deployment and submitting inputs) as callable MCP tools, so an AI client can work with Shodai agreements without custom integration code.

The server keeps no business logic and stores no credentials. Each tool call forwards the caller's API key or OAuth access token to the Agreements API gateway, which handles authentication, entitlements and metering. Signing is handled outside the server: the hosted endpoint only receives signed permit fields, while local stdio setups can optionally sign with a dev or testnet key.

It suits developers and teams building agent workflows around Shodai agreements on testnet or production, and it can be run hosted at a remote Streamable HTTP endpoint, locally over stdio, or self-hosted in a Docker container.

Tools this server provides (11)

Taken from the project documentation; the running server may differ.

list_agreements
Lists agreements via GET /v0/agreements.
get_agreement
Fetches an agreement via GET /v0/agreements/{id}.
get_agreement_document
Fetches an agreement document by ID.
get_agreement_state
Fetches agreement state.
get_input_history
Fetches the input history for an agreement.
validate_agreement
Validates an agreement template.
preflight_deployment
Runs preflight validation for a deployment.
deploy_agreement
Deploys an agreement using a signed permit.
submit_input
Submits an input to an agreement.
prepare_deployment_typed_data
Prepares EIP-712 typed data for a deployment.
prepare_input_typed_data
Prepares EIP-712 typed data for an agreement input.

What it does

Agreement lifecycle tools
Tools cover listing and reading agreements, validating templates, preflight checks, deployment and input submission.
EIP-712 typed data preparation
Helpers return the exact typed-data payload so an external signer can sign deployments and inputs.
Hosted and local transports
Runs as a remote Streamable HTTP endpoint or locally via stdio, and can be self-hosted.
OAuth or API key auth
Accepts OAuth bearer tokens with RFC 9728 discovery, or API keys matched to an environment.
Example agreements and docs
Exposes example agreement JSON, an authoring guide and a docs index as MCP resources.
Authoring prompt
Includes an author_agreement prompt that turns a business description into agreement JSON.

Good for

  • Drafting and validating Shodai agreement JSON from a plain-language business description
  • Checking a deployment with preflight before signing and deploying an agreement
  • Preparing EIP-712 payloads so an external wallet can sign deployments or inputs
  • Reading agreement state and input history from an AI client
  • Running agreement workflows in testnet automation or a self-hosted container

Shodai Agreements FAQ

Does the server store my API keys or private keys?

The README says the server stores no credentials and forwards each caller's API key or OAuth token to the gateway. The hosted endpoint receives only signed permit fields and never private keys.

Which environments are supported?

The README lists testnet and production. Testnet keys use the testnet environment and production keys use production.

How do I run Shodai Agreements locally?

The README gives an npx configuration for stdio using AGREEMENTS_API_KEY and AGREEMENTS_API_ENVIRONMENT. It can also be self-hosted over Streamable HTTP on port 3905 by default.

What license is Shodai Agreements under?

The README says this package is MIT-licensed, while other packages in the repository are Apache-2.0.

How do I add Shodai Agreements to Claude Code?

Run this command in your terminal: claude mcp add --transport http agreements https://shodai.network/mcp

What are the best alternatives to Shodai Agreements?

The closest alternatives to Shodai Agreements are Solidity Smart Contract Escrow Auditor and Smartguard MCP.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers