Build on TheTerms

API-first agreement management — for the humans on your team and the agents that work alongside them. TheTerms models agreements as structured data, with every signer decision tracked clause by clause.

REST API

OpenAPI 3.1 — every route documented and typed

• Org-scoped API keys — no separate per-user credentials to manage
• Full agreement lifecycle: containers, documents, versions, signing requests
• Templates and Webhooks for teams automating beyond the core lifecycle

View full API reference →

MCP Server

@theterms/mcp — stdio transport

• 10 tools covering the agreement lifecycle — no more, deliberately
• List/create containers and documents, draft, publish, send for signature
• Runs anywhere an MCP client does — no hosted/remote component

Jump to install →

Install the MCP server

Add this to your MCP client's config. Get an API key from your organization's settings first.

mcp-config.json

{
  "mcpServers": {
    "theterms": {
      "command": "npx",
      "args": ["-y", "@theterms/mcp"],
      "env": {
        "THETERMS_API_KEY": "tt_your_api_key_here",
        "THETERMS_API_BASE_URL": "https://app.theterms.app/api/v1"
      }
    }
  }
}

What that looks like

An agent drafting and sending an agreement, tool call by tool call.

list_containers

3 containers found

create_document

doc_8f2a created in "Customer Agreements"

publish_document

version 1.0 published

send_signing_request

invite sent to jane@acme.com

What agents can — and can't — do

An agent with an API key can draft, publish, and send agreements for signature. It cannot accept or reject a clause on a signer's behalf — no MCP tool or API endpoint exists for that. Only a human, on the signer page, can make that call.

That boundary is deliberate: consent stays human.

Known limitations

Attribution. Every action taken through an API key is attributed to the organization's owner in activity records, regardless of which team member's key was actually used — a characteristic of the REST API's current API-key auth model.
Rate limiting. The REST API enforces a per-API-key rate limit. Heavy use in a short window may hit 429 responses; the MCP server surfaces these as a clear, retryable tool error rather than crashing.

Start building

Get an API key from your organization's settings, or read the full reference before you integrate.

Get an API key → View full API reference →