English Français العربية

AddSign

Official registry Productivity

Send documents for e-signature from templates, track status, remind signers, get signed PDFs.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http addsign 'https://addsign.io/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "addsign": {
            "type": "http",
            "url": "https://addsign.io/api/mcp"
        }
    }
}
NPM package addsign-mcp
Claude Code 
claude mcp add addsign -e 'ADDSIGN_API_KEY=<your addsign_api_key>' -- npx -y addsign-mcp@0.1.5
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "addsign": {
            "command": "npx",
            "args": [
                "-y",
                "addsign-mcp@0.1.5"
            ],
            "env": {
                "ADDSIGN_API_KEY": "<your addsign_api_key>"
            }
        }
    }
}

Environment variables

  • ADDSIGN_API_KEY required secret AddSign API key — create one at https://addsign.io/settings/api

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. addsign-mcp
  2. Setup
  3. Tools
  4. A typical agent flow
  5. Error semantics
  6. Development

addsign-mcp

MCP server for AddSign — lets AI agents send documents for signature, track signing status, remind signers, and download signed, hash-verifiable PDFs.

Stateless by design: it speaks only AddSign's public v1 API with your API key. No database access, no shared secrets. Revoking the key at addsign.io/settings/api kills the integration instantly.

Setup

  1. Create an API key at addsign.io → Settings → API Keys (free on every plan; Free includes 8 documents/month).
  2. Set it in the environment — never in prompts or config committed to git:
export ADDSIGN_API_KEY=sk_...
Claude Code
claude mcp add addsign --env ADDSIGN_API_KEY=sk_... -- npx -y addsign-mcp

(Until the npm package is published, point at a checkout instead: claude mcp add addsign --env ADDSIGN_API_KEY=sk_... -- node /path/to/simple-sign/mcp/dist/index.js)

Claude Desktop (claude_desktop_config.json)
{
  "mcpServers": {
    "addsign": {
      "command": "node",
      "args": ["/path/to/simple-sign/mcp/dist/index.js"],
      "env": { "ADDSIGN_API_KEY": "sk_..." }
    }
  }
}
Environment
VariableRequiredDefaultPurpose
ADDSIGN_API_KEYyes—Your AddSign API key (sk_...)
ADDSIGN_BASE_URLnohttps://addsign.ioPoint at a different deployment

Tools

ToolKindWhat it does
list_templatesreadTemplates + the signer roles each expects + field summary
send_for_signaturewriteCreate from template + email signers; idempotent via request_id
check_statusreadDocument + per-signer state + recent audit events
download_signedread5-minute signed URL + the ledger's SHA-256 for verification
remindwriteNudge pending signers (4h per-signer server-side cooldown)
list_documentsreadPaginated document list, filterable by status

No destructive tools: an agent cannot cancel or delete a legal document through this server.

A typical agent flow

list_templates                      → find "Contract to Lease", roles: [tenant_1, tenant_2]
send_for_signature {template_id,
  signers: [Artem…, Valeria…],
  request_id: <uuid>}               → document_id, status: pending, usage 3/8
check_status {document_id}          → Artem signed, Valeria viewed
remind {document_id, valeria@…}     → reminded (or skipped: reminded_recently)
download_signed {document_id}       → url + sha256 → fetch, verify, file it

Error semantics

Every AddSign error carries a stable error_code; this server appends the right next step for the agent. The two that matter most:

  • rate_limited (429) — back off retry_after seconds, retry.
  • plan_limit_reached (402) — never retry; the monthly cap resets on the 1st or the human upgrades.

Development

cd mcp
npm install
npm run build     # → dist/index.js
ADDSIGN_API_KEY=sk_... node dist/index.js

Frequently asked questions

What is AddSign?

Send documents for e-signature from templates, track status, remind signers, get signed PDFs.

How do I install AddSign?

It runs as a remote server. In Claude Code: claude mcp add --transport http addsign 'https://addsign.io/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does AddSign need an API key?

Yes. It expects ADDSIGN_API_KEY, which you set in its configuration.

Is AddSign open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains AddSign?

It is published by rmindgh. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.