# AddSign [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/rmindgh/addsign-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/addsign

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

## Tools
Capabilities this server exposes over MCP:

- **list_templates** — Templates + the signer roles each expects + field summary
- **send_for_signature** — Create from template + email signers; idempotent via `request_id
- **check_status** — Document + per-signer state + recent audit events
- **download_signed** — 5-minute signed URL + the ledger's SHA-256 for verification
- **remind** — Nudge pending signers (4h per-signer server-side cooldown)
- **list_documents** — Paginated document list, filterable by status

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "addsign": {
    "command": "npx",
    "args": ["-y","addsign-mcp"],
    "env": {
      "ADDSIGN_API_KEY": "",
      "ADDSIGN_BASE_URL": ""
    }
  }
}
```

**Requires environment variables:** `ADDSIGN_API_KEY`, `ADDSIGN_BASE_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the AddSign MCP server does

The AddSign MCP server gives an MCP-compatible agent access to AddSign’s document-signing workflow. It can inspect available templates, see the signer roles and fields those templates expect, create signature requests, monitor progress, remind pending recipients, list documents, and retrieve completed PDFs.

The server works against AddSign’s public v1 API rather than a local database. It is stateless and uses the API key supplied at runtime. Revoking that key in AddSign settings immediately disables the integration. Agents cannot cancel or delete legal documents through these tools.

## How it works

A typical workflow starts with `list_templates`, which returns templates, expected signer roles, and a field summary. The agent can then call `send_for_signature` with a template, signer email details, and a `request_id`. The request ID makes creation idempotent, reducing the chance of duplicate documents when an operation is retried.

After creation, `check_status` reports the document state, each signer’s state, and recent audit events. `remind` can nudge a pending signer, subject to a four-hour server-side cooldown for each signer. Once signing is complete, `download_signed` returns a signed URL that remains valid for five minutes along with the SHA-256 value recorded in AddSign’s ledger. The downloaded file can be checked against that hash before it is stored or processed.

Errors include stable error codes and a suggested next action. A `rate_limited` response should be retried after the supplied `retry_after` interval. A `plan_limit_reached` response should not be retried; the monthly allowance resets on the first day of the month or after an account upgrade.

## Setup and configuration

Create an AddSign API key under AddSign’s Settings and API Keys area, then provide it through `ADDSIGN_API_KEY`. The key should stay out of prompts and configuration files committed to source control. AddSign’s Free plan includes eight documents per month, according to the supplied setup notes.

For Claude Code, the documented command runs `npx -y addsign-mcp` with the key passed as an environment variable. Until the npm package is published, the setup instructions provide a fallback that runs the built `dist/index.js` file from a local checkout. Claude Desktop can use the same local entry point in its MCP configuration. `ADDSIGN_BASE_URL` is optional and defaults to `https://addsign.io`; set it when targeting another deployment.

## Tools and capabilities

The AddSign MCP server exposes six tools:

- `list_templates`: Read templates, signer roles, and field summaries.
- `send_for_signature`: Create a document from a template and email its signers.
- `check_status`: Read document, signer, and recent audit-event status.
- `download_signed`: Obtain a temporary signed URL and the ledger SHA-256.
- `remind`: Notify a pending signer, subject to the cooldown.
- `list_documents`: Browse paginated documents and filter by status.

Four tools are read operations and two create side effects: sending a request and reminding a signer. No tool deletes or cancels a legal document.

## Limitations and notes

The AddSign MCP server requires a valid AddSign API key and access to the configured API endpoint. Its document volume is subject to the account’s monthly plan limit. Download URLs expire after five minutes, so an agent should fetch the file promptly and verify its hash while the URL is valid. Reminder requests may be skipped when the same signer was reminded within the four-hour cooldown.

_Full upstream README: https://allmcps.com/mcp/addsign/readme_