AddSign

io.github.rmindghPublished by GitHub account rmindghv0.1.5Updated Oct 28, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

AddSign MCP server lets an assistant send documents for e-signature from templates, track signer status, remind signers and fetch signed PDFs.

What you can do
  • List templates with their expected signer roles and field summaries
  • Send a document for signature from a template and email the signers, idempotent via a request ID
  • Check a document's status, per-signer state and recent audit events, and list documents filtered by status
  • Remind pending signers, subject to a server-side cooldown
  • Get a short-lived signed download URL plus the SHA-256 hash for verifying the signed PDF
When to use it
Useful when an assistant should handle e-signature paperwork end to end: preparing a contract from a template, sending it to signers, following progress, nudging people who have not signed, and retrieving the finished PDF for filing.
Requirements
A remote endpoint at addsign.io or the local npm package addsign-mcp run with Node.js; an AddSign account and API key supplied in the ADDSIGN_API_KEY environment variable; OAuth is declared as required; network access to the AddSign API. The optional ADDSIGN_BASE_URL variable points at a different deployment.
Before you install
The API key is a secret: keep it in the environment, not in prompts or committed config, and revoke it at the provider's settings page if exposed. Sending and reminding are write actions that email real signers. Usage is capped by plan (Free includes 8 documents per month); a plan_limit_reached error means the cap is hit and should not be retried. Document content and signer details go to AddSign as a third party. No tools cancel or delete documents.

Installation

In SourceWeft

  1. Open AddSign in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.rmindgh%2Faddsign-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "addsign": {
      "type": "http",
      "url": "https://addsign.io/api/mcp"
    }
  }
}

README

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/8check_status {document_id}          → Artem signed, Valeria viewedremind {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 mcpnpm installnpm run build     # → dist/index.jsADDSIGN_API_KEY=sk_... node dist/index.js

Source: README.md at commit fb75f2c

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.1.5LatestOct 3, 2026
  2. v0.1.4Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts