Odel
MCP server: One MCP server.

AddSign

@rmindghMCP server · External

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

E-signaturesv0.1.5MITTypeScript
Freeno charge per call
Sign in to install

One address for any MCP client. You sign in at ojfkehzjcfakwmtvtsjr.supabase.co once, after adding it.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: moves money, runs code or commands, deletes data, or sends messages for you.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Tools

None listed · checked 3 Oct 2026

Odel could not list its tools without signing in.

Try it in the Inspector
README2 min read

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:
bash
export ADDSIGN_API_KEY=sk_...

Claude Code

bash
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)

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

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

Similar modules

Browse E-signatures