Skip to main content
ClaudeWave

MCP server + Claude Desktop Extension for AddSign — agents send documents for e-signature, track status, and download signed PDFs

MCP ServersRegistry oficial0 estrellas0 forks● TypeScriptMITActualizado today
ClaudeWave Trust Score
87/100
✓ Trusted
Passed
  • ✓Open-source license (MIT)
  • ✓Actively maintained (<30d)
  • ✓Clear description
  • ✓Documented (README)
Last scanned: 10/3/2026
Install in Claude Code / Claude Desktop
Method: NPX · addsign-mcp
Claude Code CLI
claude mcp add addsign-mcp -- npx -y addsign-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "addsign-mcp": {
      "command": "npx",
      "args": ["-y", "addsign-mcp"],
      "env": {
        "ADDSIGN_API_KEY": "<addsign_api_key>"
      }
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Detected environment variables
ADDSIGN_API_KEY
Casos de uso

Resumen de MCP Servers

# addsign-mcp

MCP server for [AddSign](https://addsign.io) — 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](https://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

| Variable | Required | Default | Purpose |
|---|---|---|---|
| `ADDSIGN_API_KEY` | yes | — | Your AddSign API key (`sk_...`) |
| `ADDSIGN_BASE_URL` | no | `https://addsign.io` | Point at a different deployment |

## Tools

| Tool | Kind | What it does |
|---|---|---|
| `list_templates` | read | Templates + the signer roles each expects + field summary |
| `send_for_signature` | write | Create from template + email signers; idempotent via `request_id` |
| `check_status` | read | Document + per-signer state + recent audit events |
| `download_signed` | read | 5-minute signed URL + the ledger's SHA-256 for verification |
| `remind` | write | Nudge pending signers (4h per-signer server-side cooldown) |
| `list_documents` | 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 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
```

Lo que la gente pregunta sobre addsign-mcp

¿Qué es rmindgh/addsign-mcp?

+

rmindgh/addsign-mcp es mcp servers para el ecosistema de Claude AI. MCP server + Claude Desktop Extension for AddSign — agents send documents for e-signature, track status, and download signed PDFs Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-10-03.

¿Cómo se instala addsign-mcp?

+

Puedes instalar addsign-mcp clonando el repositorio (https://github.com/rmindgh/addsign-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar rmindgh/addsign-mcp?

+

Nuestro agente de seguridad ha analizado rmindgh/addsign-mcp y le ha asignado un Trust Score de 87/100 (tier: Trusted). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene rmindgh/addsign-mcp?

+

rmindgh/addsign-mcp es mantenido por rmindgh. La última actividad registrada en GitHub es del 2026-10-03, con 0 issues abiertos.

¿Hay alternativas a addsign-mcp?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega addsign-mcp en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: rmindgh/addsign-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/rmindgh-addsign-mcp)](https://claudewave.com/repo/rmindgh-addsign-mcp)
<a href="https://claudewave.com/repo/rmindgh-addsign-mcp"><img src="https://claudewave.com/api/badge/rmindgh-addsign-mcp" alt="Featured on ClaudeWave: rmindgh/addsign-mcp" width="320" height="64" /></a>

Más MCP Servers

Alternativas a addsign-mcp