Docs
Dashboard Get an API key

MCP server

Tools

The ten MCP tools at a glance, with what each one does, whether it changes anything, and its REST equivalent.

Each tool answers with JSON text in the same shapes as the REST API, so what you learn in the API reference applies here too.

Reading

These tools change nothing, so clients run them without asking.

Tool What it does REST equivalent
get_account Plan, documents left, verified domains. Get account
list_templates The saved templates. List templates
get_template One template and its fields. Get a template
list_pacts Pacts by status (default active). List pacts
get_pact One pact in full. Get a pact
get_signing_status Who has signed, who is next. (MCP only)

Changing

These tools change your pacts, and most clients ask you before running them.

Tool What it does REST equivalent
create_pact Create a pact from a template, and optionally send it. Sending uses documents. Create a pact
send_pact Send a draft. Uses documents. Send a pact
resend_pact Email the current signer a fresh link. Resend the signing link
void_pact Withdraw a pact. Destructive; cannot be undone. Void a pact

Differences from the API

  • list_templates returns a plain array; the API wraps it in { "data", "total" }.
  • list_pacts defaults to active (drafts and sent) and has no offset; the API defaults to all and pages.
  • create_pact only sends saved templates, and takes recipients as a JSON string. Uploading a document is done with the API or the dashboard.
  • get_signing_status is MCP only: a compact summary that is cheaper for a model to read than the whole pact.
  • There are no tools for downloading PDFs or deleting drafts. Use the API for those.