MCP server + Claude Desktop Extension for AddSign — agents send documents for e-signature, track status, and download signed PDFs
- ✓Open-source license (MIT)
- ✓Actively maintained (<30d)
- ✓Clear description
- ✓Documented (README)
claude mcp add addsign-mcp -- npx -y addsign-mcp{
"mcpServers": {
"addsign-mcp": {
"command": "npx",
"args": ["-y", "addsign-mcp"],
"env": {
"ADDSIGN_API_KEY": "<addsign_api_key>"
}
}
}
}ADDSIGN_API_KEYMCP Servers overview
# 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
```
What people ask about addsign-mcp
What is rmindgh/addsign-mcp?
+
rmindgh/addsign-mcp is mcp servers for the Claude AI ecosystem. MCP server + Claude Desktop Extension for AddSign — agents send documents for e-signature, track status, and download signed PDFs It has 0 GitHub stars and its last recorded update is dated 2026-10-03.
How do I install addsign-mcp?
+
You can install addsign-mcp by cloning the repository (https://github.com/rmindgh/addsign-mcp) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.
Is rmindgh/addsign-mcp safe to use?
+
Our security agent has analyzed rmindgh/addsign-mcp and assigned a Trust Score of 87/100 (tier: Trusted). See the full breakdown of passed checks and flags on this page.
Who maintains rmindgh/addsign-mcp?
+
rmindgh/addsign-mcp is maintained by rmindgh. The last recorded GitHub activity is dated 2026-10-03, with 0 open issues.
Are there alternatives to addsign-mcp?
+
Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.
Deploy addsign-mcp to your cloud
Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.
Maintain this repo? Add a badge to your README
Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.
[](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>More MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
The fastest path to AI-powered full stack observability, even for lean teams.