MCP server

eContract runs a remote Model Context Protocol server. AI clients that speak MCP can send contracts for e-signature, follow signing, hand out signing links and fetch signed PDFs and audit trails, without custom code.

https://api.econtract.online/mcp

• Transport: Streamable HTTP, stateless, POST /mcp (protocol 2026-07-28; clients that still start with initialize are served too). GET and DELETE /mcp answer 405 (after authentication).
• Signing is always human. No tool signs or declines; the agent gives each signer their own link and the person signs.

Authentication

Every request needs Authorization: Bearer <token>, either:

• OAuth 2.1 (recommended for apps people connect): the client discovers everything from the server's 401 answer and runs the OAuth flow in the browser. The user signs in, picks a workspace and approves the scopes. Tokens are eco_at_… and must be issued for the resource https://api.econtract.online/mcp.
• An API key cl_live_… (headless agents, CI, CLI configs with a fixed header), created under Dashboard → API Keys.

A request without a valid token gets:

HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer resource_metadata="https://api.econtract.online/.well-known/oauth-protected-resource/mcp", scope="contracts:read contracts:write templates:read files:read files:write ai:use"

error="invalid_token" is added when a token was sent but is not valid. The protected resource metadata points to the authorization server https://api.econtract.online.

The MCP server checks every token with eContract and never forwards it; tool calls reach the contract API with the same identity, scopes and role cap as REST calls.

Tools

Also a resource template econtract://contracts/{contractId}/document/{version} (contracts:read).

• Write tools take an optional idempotencyKey. Without it the server generates one and returns it, so the model can repeat a call safely (see Idempotency).
• Documents passing through the connector (uploads and downloads) are limited to 10 MB; larger files must be uploaded with fileUrl or downloaded in the eContract app.
• API errors come back as tool results with isError: true, the error code, message, requestId and a hint for the model.

Typical workflow

1. list_templates / get_template, or take the user's PDF or DOCX.
2. send_contract, after confirming title, document and signers with the user. It returns processingStatus: "processing".
3. Poll get_contract until processingStatus is ready.
4. With delivery: "link" or "both": get_signing_links, and give each signer only their own link.
5. While waiting: get_contract, send_reminder; void_contract to cancel.
6. When status is completed: download_signed_document and get_audit_trail.

Connect your client

Server URL: https://api.econtract.online/mcp. OAuth clients only need the URL; they find the rest themselves.

Claude.ai and Claude Desktop

Settings → Connectors → Add custom connector, URL https://api.econtract.online/mcp, then Connect and approve the consent screen. (Menu names: verify against the current Claude UI.)

Claude Code

# OAuth (opens the browser on first use; or run /mcp inside Claude Code)
claude mcp add --transport http econtract https://api.econtract.online/mcp

# API key
claude mcp add --transport http econtract https://api.econtract.online/mcp \
  --header "Authorization: Bearer cl_live_..."

Project-scoped .mcp.json:

{
  "mcpServers": {
    "econtract": {
      "type": "http",
      "url": "https://api.econtract.online/mcp",
      "headers": { "Authorization": "Bearer ${ECONTRACT_API_KEY}" }
    }
  }
}

ChatGPT

Enable Developer mode (Settings → Apps & Connectors → Advanced), then Create a connector with URL https://api.econtract.online/mcp and authentication OAuth. (Menu names: verify against the current ChatGPT UI.)

Cursor

~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "econtract": { "url": "https://api.econtract.online/mcp" }
  }
}

Add "headers": { "Authorization": "Bearer cl_live_..." } to use an API key instead of OAuth. (Verify against the current Cursor docs.)

VS Code (GitHub Copilot agent mode)

.vscode/mcp.json:

{
  "servers": {
    "econtract": { "type": "http", "url": "https://api.econtract.online/mcp" }
  }
}

VS Code runs the OAuth flow when the server answers 401. For an API key add "headers": { "Authorization": "Bearer ${input:econtract-key}" } with a matching inputs entry. (Verify against the current VS Code docs.)

Your own agent or the MCP Inspector

Any MCP client with Streamable HTTP works. To try the tools by hand: npx @modelcontextprotocol/inspector, transport Streamable HTTP, URL https://api.econtract.online/mcp, header Authorization: Bearer cl_live_….

Troubleshooting