English Français العربية

AddSign

Registre officiel Productivité

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

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http addsign 'https://addsign.io/api/mcp'
Configuration JSON (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
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "addsign": {
            "command": "npx",
            "args": [
                "-y",
                "addsign-mcp@0.1.5"
            ],
            "env": {
                "ADDSIGN_API_KEY": "<your addsign_api_key>"
            }
        }
    }
}

Variables d'environnement

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

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  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

Questions fréquentes

Qu'est-ce que AddSign ?

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

Comment installer AddSign ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http addsign 'https://addsign.io/api/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour AddSign ?

Oui. Il attend ADDSIGN_API_KEY, à renseigner dans sa configuration.

AddSign est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient AddSign ?

Il est publié par rmindgh. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.