addsign-mcp
addsign-mcp is a stateless MCP server that lets AI agents send documents for signature through AddSign's public v1 API using your own API key.
Browse templates (
list_templates) — see available templates, the signer roles each expects, and a summary of pre-placed fields (filled by signers, not the sender).Send documents for signature (
send_for_signature) — create from a template and email signers; roles are assigned by array position (max 10). Supports adry_runpreview, a personalmessage, and parallel or sequential signing order. Idempotent viarequest_idso retries don't double-send.Track status (
check_status) — overall document state, per-signer state (viewed/signed/declined with timestamps and reasons), and recent audit-trail events.Download signed PDFs (
download_signed) — get a 5-minute signed URL plus the ledger's SHA-256 hash for verifying the evidentiary original.Remind signers (
remind) — nudge all pending signers or one by email, with a server-side 4-hour per-signer cooldown.List documents (
list_documents) — paginated, newest-first list filterable by status (including a virtualdeclinedfilter), with decline details reported.Safety limits — read-only or non-destructive tools only; an agent cannot cancel or delete a legal document.
Stable error semantics — e.g.
rate_limited(back offretry_after, retry) andplan_limit_reached(never retry; monthly cap resets on the 1st or human upgrades).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@addsign-mcp Send template 'NDA' to jane@example.com for signature"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Create an API key at addsign.io → Settings → API Keys (free on every plan; Free includes 8 documents/month).
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
Variable | Required | Default | Purpose |
| yes | — | Your AddSign API key ( |
| no |
| Point at a different deployment |
Related MCP server: Formify MCP
Tools
Tool | Kind | What it does |
| read | Templates + the signer roles each expects + field summary |
| write | Create from template + email signers; idempotent via |
| read | Document + per-signer state + recent audit events |
| read | 5-minute signed URL + the ledger's SHA-256 for verification |
| write | Nudge pending signers (4h per-signer server-side cooldown) |
| read | Paginated 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 itError 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 offretry_afterseconds, 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.jsAvailable Tools
6 toolscheck_statusCheck document statusARead-onlyInspect
Get the current state of a document: overall status, each signer (viewed / signed / declined, with timestamps and decline reasons), and the recent audit-trail events. This is the polling surface — call it when the human asks "did they sign?".
Inputs: document_id (required).
download_signedDownload the signed PDFARead-onlyInspect
Get a short-lived (5 min) download URL for the signed PDF, plus the SHA-256 hash the audit ledger recorded at signing. Give the human the URL to download; the hash lets them (or any tool) verify the file is the evidentiary original. Only fetch the URL yourself if your environment permits network access to addsign.io — many sandboxes do not. Only works once the document status is signed.
Inputs: document_id (required), artifact.
list_documentsList documentsARead-onlyInspect
List the sender's documents, newest first, optionally filtered by status. Each row carries declined_by (name, email, reason) when a signer declined — such envelopes have status 'cancelled', but ALWAYS report them to the human as declined, with the reason. Paginate with limit/offset (limit max 100).
Inputs: limit, offset, status.
list_templatesList templatesARead-onlyInspect
List the sender's document templates. Each template carries the signer roles it expects (fill exactly these, in order, when calling send_for_signature) and a summary of its pre-placed fields — those fields are completed by the SIGNERS at signing time; they cannot be prefilled by the sender. Start here to find what can be sent.
Inputs: no named parameters.
remindRemind pending signersAInspect
Send a reminder email to signers who have not signed yet (all of them, or one by email). Server-side throttling applies: a signer reminded in the last 4 hours is skipped, not re-emailed — the response lists who was reminded and who was skipped.
Inputs: document_id (required), signer_email.
send_for_signatureSend a document for signatureAInspect
Create a document from a template and email it to signers for signature. IMPORTANT: sending exposes the document contents to every listed email — NEVER guess or infer a signer email address. Use exactly the emails the human gave you; if any is missing or ambiguous, ask the human before calling this tool, and restate the recipient list in your confirmation. ARRAY POSITION assigns template roles: the first signer gets the first role, and so on. The document sends as-is — its fields are filled by the signers at signing, not by you. Returns the document id — poll check_status with it. Pass a stable request_id when you might retry: a replayed request returns the original document instead of double-sending. A mis-sent envelope can be voided by the human from the AddSign dashboard (Cancel).
Inputs: signers (required), template_id (required), title, dry_run, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct action: checking status, downloading signed documents, listing documents, listing templates, sending reminders, and sending for signature. No overlap in purpose.
All tool names follow a consistent verb_noun pattern with underscores, e.g., check_status, download_signed, list_documents. Even 'remind' is a verb alone but fits the pattern of single-action tools.
With 6 tools, the set is well-scoped for a document signing server. It covers listing, sending, and managing documents without being overly sparse or bloated.
The tool set covers the core workflow: list templates, send for signature, check status, remind, and download. Minor gaps exist, such as no tool to create templates or void documents (must be done via dashboard), but these are acceptable for the focused scope.
Maintenance
Related MCP Connectors
Send documents for e-signature from AI assistants, track signers, and download sealed, signed PDFs.
Send PDFs for e-signature from your AI assistant, track status and get the signed copy.
Send AI-created PDFs for signature, track signers, and return verifiable document evidence.
Contracts and e-signature for AI agents: draft from templates, fill fields, send, track signing.
1
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.12252 npm1MIT

Formify MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to create fillable PDFs, send contracts for e-signature, verify signers via BankID or ID scans, and track post-send document workflows.5MIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create fillable PDF forms, send contracts for electronic signature, verify signer identity via BankID or ID scan, and track document status after sending.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and developers to create, send, and follow up on contracts for e-signature, manage signers and templates, retrieve signed PDFs and audit trails, and verify PDF signatures. It keeps signing and declining in the hands of each signer through personal links.1MIT