APISign MCP server

APISign MCP Server

Send documents out for legally binding e-signature, and manage the templates they come from, directly from an AI agent.

APISign runs a hosted Model Context Protocol server at https://apisign.io/mcp. There is nothing to install and nothing to self-host — point your client at the URL, give it an API key, and your agent can draft a contract from a template, fill its variables, send it to signers, and watch the signatures come in.

This repository holds the connection metadata and client configuration. The service itself lives at apisign.io.

Connect

1. Get an API key. Sign in at apisign.io, then go to Account → API Keys and create one. Copy it — it is shown once.

Pick the permission deliberately:

A Read Only key does not merely refuse the write tools — they are left out of the tools/list response entirely, so the agent never learns they exist. If your agent only needs to look things up, use one.

2. Add the server. The quickest route, which works for Claude, Cursor, ChatGPT and most other clients:

npx add-mcp https://apisign.io/mcp --header '{"x-api-key": "your-api-key-here"}'

Or configure it by hand:

{
  "mcpServers": {
    "apisign": {
      "url": "https://apisign.io/mcp",
      "headers": {
        "x-api-key": "your-api-key-here"
      }
    }
  }
}

Transport is Streamable HTTP. Authentication is the x-api-key header.

Tools

Twelve tools, in two families. Everything is scoped to the organization the API key belongs to.

Templates

Contracts

Templates are Markdown with Handlebars-style variables — {{clientname}}, {{effectivedate}} — that contractcreate fills in. Signature placeholders work the same way: a one-signer document needs a {{signature}}, and a multi-signer document gives each party their own, assigned through signerfields.

A worked example

Draft an NDA for Acme Corp from our standard mutual NDA template, effective

the first of next month, and send it to legal@acme.example and to me.

Shortened. The full README is on GitHub.