addsign-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@addsign-mcpSend template 'NDA' to jane@example.com for signature"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
addsign-mcp
MCP server for AddSign — connect Claude (or any MCP client) to your AddSign account so your AI assistant can send documents for e-signature, track signing status, remind pending signers, and download signed PDFs with their audit-trail hashes.
Built and maintained by Gold Bird INC, the maker of AddSign.
Install
Every path needs an AddSign account (free plan included) — get connection instructions tailored to your client, with your API key filled in, at addsign.io/settings/api.
Claude Desktop (one-click, works on the free Claude plan): download the Desktop Extension (.mcpb) and double-click it (or drag it into Claude Desktop). You'll be prompted for your API key — it's stored in your system keychain, never in a file.
claude.ai / Claude Desktop via hosted connector (no key at all): Settings → Connectors → Add custom connector → https://addsign.io/api/mcp, then authorize with your AddSign login (OAuth). Paid Claude plans.
Claude Code:
claude mcp add addsign --env ADDSIGN_API_KEY=sk_your_key -- npx -y addsign-mcpAny other MCP client (Cursor, VS Code, Windsurf, Gemini CLI, Codex CLI, …):
{
"mcpServers": {
"addsign": {
"command": "npx",
"args": ["-y", "addsign-mcp"],
"env": { "ADDSIGN_API_KEY": "sk_your_key" }
}
}
}Related MCP server: layerone-mcp
Tools
Tool | What it does |
| Your templates, their signer roles, and field summaries |
| Create a document from a template and email it to signers (supports |
| Who viewed / signed / declined, with the audit trail |
| Nudge signers who haven't signed (server-throttled) |
| Short-lived URL for the signed PDF + its ledger SHA-256 |
| Your documents, filterable by status (including |
Security posture
The server holds no secrets beyond your own API key, read from the
ADDSIGN_API_KEYenvironment variable only — never from prompts or tool arguments — and redacted from every error it surfaces. It speaks only AddSign's public v1 API; there is no database access.No destructive tools. An agent can send, but can never cancel or delete documents, touch account or billing settings, or see API keys. Mis-sends are corrected by the human — every agent-initiated send emails the account owner with one-click View/Cancel.
Server-side guardrails on every agent send: recipient verification (deliverability, saved-contacts matching, typo detection), optional per-key contacts-only restriction, plan metering, and full audit-ledger attribution of every agent action.
Keys are created and revoked instantly at addsign.io/settings/api.
Development
npm install
npm run build # compile TypeScript → dist/
npm run build:mcpb # build the Claude Desktop Extension → addsign.mcpbRequires Node.js ≥ 18. The .mcpb build bundles the server into a single file (no node_modules shipped) and packs it with @anthropic-ai/mcpb.
This repository is the public release mirror of the server that ships as addsign-mcp on npm and in the official MCP Registry (io.github.rmindgh/addsign-mcp). Issues and questions are welcome here; the AddSign product itself is not open source.
License
MIT © Gold Bird INC
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.Last updated8411MIT

layerone-mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to generate documents (PDF/DOCX/Factur-X) and manage electronic signatures (eIDAS/PAdES) via natural language using LayerOne's DocX and Sign APIs.Last updated2040MIT- AlicenseAqualityBmaintenanceEnables AI clients to create and manage e-signature sessions, envelopes, documents, and webhooks through the SignDocs Brasil API.Last updated2474MIT
- AlicenseAqualityCmaintenanceExposes the SumoSign signing API to AI agents, allowing document upload, envelope creation, and tracking, with signing always done by human recipients.Last updated1529MIT
Related MCP Connectors
Automate eSignature workflows and signing tasks via natural language commands.
SignDocs Brasil e-signature tools for AI agents — signing sessions, envelopes, verification.
Document API for AI-native software: render PDFs, e-sign, PAdES-seal, and verify.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rmindgh/addsign-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server