mcp-server-esignatures MCP server

What is mcp-server-esignatures?

mcp-server-esignatures is an MCP server that gives AI agents direct access to the eSignatures.com API. It enables dynamic, Markdown-based electronic signature workflows — from contract creation and editing to signing and amendments — without relying on rigid PDF files.

How to use mcp-server-esignatures?

Install via uvx mcp-server-esignatures and set the ESIGNATURES_SECRET_TOKEN environment variable with your eSignatures.com API secret token. Configure it in Claude Desktop’s claude_desktop_config.json under the mcpServers key. Then you can ask the AI to create, send, edit, or manage contracts using natural language commands.

Key features of mcp-server-esignatures

• Create, query, withdraw, and delete contracts
• Add, update, resend, and delete contract signers
• Query and update placeholder fields on active contracts
• Retrieve and edit contract content in Markdown format
• Create, update, query, and delete contract templates
• Manage template collaborators (invite, remove, list)

Use cases of mcp-server-esignatures

• Draft a contract using Markdown, then review and send it to signers
• Send a contract from an existing template with custom field values
• Edit an active contract’s wording after it has been sent
• Update signer contact details or resend signature requests
• Manage and improve templates with AI‑assisted suggestions

FAQ from mcp-server-esignatures

What makes this different from traditional eSignature tools?

Traditional tools lock contracts into rigid PDFs. eSignatures.com keeps contracts as fully editable Markdown content, making them easy for AI to create, understand, and modify throughout their lifecycle.

What runtime does the server require?

The server runs with uv (development) or uvx (published). Python must be installed along with the mcp-server-esignatures package, which is fetched automatically by uvx.

How do I authenticate with the eSignatures API?

Set the ESIGNATURES_SECRET_TOKEN environment variable to your eSignatures.com API secret token. No other authentication method is required.

Where is my contract data stored?

All contracts, templates, and signer data are stored on eSignatures.com’s servers. The MCP server only mediates API calls.

Are there any known limitations?

The README does not mention specific limits. However, capabilities depend on the underlying eSignatures.com API and the server’s defined tools (e.g., no bulk operations or complex multi‑party workflows beyond what’s listed).