eSignatures

The most developer- and AI-friendly electronic signature platform.

Traditional eSignature tools lock you into rigid, static PDF files. eSignatures.com takes a different approach — contracts remain fully editable, Markdown-based content throughout their entire lifecycle, making them effortless for developers, automation systems, and AI agents to create, understand, modify, and manage.

This MCP server gives AI agents (such as Claude) real-time access to the complete eSignatures API, enabling:

• Dynamic contract creation and editing — even after sending
• Markdown-based content that AI can generate, understand, and update
• End-to-end workflows: drafting → placeholder filling → sending → signing → amendments
• Flexible templates and reusable contract workflows
• Contract links: reusable public signing URLs for waivers, NDAs and onboarding forms
• Signer management, notifications, and lifecycle automation

Built for intelligent, adaptive contract workflows — not outdated PDF-based signing.

Create a draft NDA for a publisher, ready for me to review and send. Signer: John Doe, ACME Corp, john@acme.com.

Send the draft NDA for John Doe now.

Send an NDA based on my template to John Doe from ACME Corp at john@acme.com. Set the term to 2 years.

Create a contractor agreement for a graphic designer, including payment terms of net 14 days. Prepare it as a draft for review. Signer: John Doe, ACME Corp, john@acme.com.

Add Jane Smith from ACME Corp (jane@acme.com) as a signer on the NDA contract, then send her the signature request.

On the NDA, change the term to 24 months and remove the jurisdiction section.

Show me the NDA as it was before the term changed.

Update my NDA template to include a 12-month non-solicitation clause.

Review my templates and suggest improvements. Do not apply any changes until I approve them one by one.

Find the best template for onboarding a contractor and prepare a draft contract for John Doe.

Show me the recent contracts that are waiting for signatures.

Update the signer email on the NDA contract for John Doe to john.doe@acme.com.

Turn my waiver template into a contract link, verify signers by SMS, and CC office@acme.com on every signed copy.

List my contract links and flag any still in test mode.

Invite John Doe to edit the NDA template. His email is john@acme.com.

Prefer not to run anything locally? Connect any MCP client to https://esignatures.com/mcp (Streamable HTTP, OAuth). Claude, ChatGPT and other clients are covered at https://esignatures.com/docs/mcp.

Create an eSignatures.com account at https://esignatures.com for free, then copy your API secret token from the Automation & API page.

On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

"mcpServers": {
  "mcp-server-esignatures": {
    "command": "uv",
    "env": {
      "ESIGNATURES_SECRET_TOKEN": "your-esignatures-api-secret-token"
    },
    "args": [
      "--directory",
      "/your-local-directories/mcp-server-esignatures",
      "run",
      "mcp-server-esignatures"
    ]
  }
}

"mcpServers": {
  "mcp-server-esignatures": {
    "command": "uvx",
    "args": [
      "mcp-server-esignatures"
    ],
    "env": {
      "ESIGNATURES_SECRET_TOKEN": "your-esignatures-api-secret-token"
    }
  }
}

To use this server, you need to set the ESIGNATURES_SECRET_TOKEN environment variable with your eSignatures.com API secret token.

For a detailed guide on API endpoints, parameters, and responses, see eSignatures.com API.

For support, please navigate to Support or contact support@esignatures.com.

Contributions are welcome! If you'd like to contribute, please fork the repository and make changes as you see fit. Here are some guidelines:

• Bug Reports: Please open an issue to report any bugs you encounter.
• Feature Requests: Suggest new features by opening an issue with the "enhancement" label.
• Pull Requests: Ensure your pull request follows the existing code style.
• Documentation: Help improve or translate documentation. Any form of documentation enhancement is appreciated.

For major changes, please open an issue first to discuss what you would like to change. We're looking forward to your contributions!