Mcp Server Esignatures

What is Mcp Server Esignatures about?

Mcp Server Esignatures provides a suite of MCP tools that let users draft, send, query, withdraw, and delete electronic contracts, as well as manage contract templates and collaborators. It connects to the eSignatures platform via a secret API token.

How to use Mcp Server Esignatures?

1. Create an eSignatures account and obtain an API secret token.
2. Set the environment variable ESIGNATURES_SECRET_TOKEN with the token.
3. Run the server (using the provided development or published configuration).
4. Call the MCP tools such as create_contract, list_templates, add_template_collaborator, etc., either via the MCP client or programmatically through the API.

Key Features of Mcp Server Esignatures

• Contract Lifecycle Management: create drafts, send for signature, query status, withdraw, delete.
• Template Management: create, update, retrieve, list, and delete contract templates.
• Collaborator Controls: invite, remove, and list collaborators who can edit templates.
• Simple Authentication: single secret token passed via environment variable.
• Ready‑to‑use MCP tooling: pre‑defined tool definitions with clear categories.

Use Cases of Mcp Server Esignatures

• Legal teams generating NDAs, service agreements, and other contracts quickly.
• Sales departments automating contract sending and tracking for deals.
• HR departments managing employment agreements and onboarding paperwork.
• Freelancers creating reusable templates for recurring client work.
• Product teams collaborating on template updates with role‑based permissions.

FAQ for Mcp Server Esignatures

Q: Which programming language is required? A: The server runs as a Python package (invoked via uv or uvx).

Q: How do I obtain the ESIGNATURES_SECRET_TOKEN? A: Sign up at https://esignatures.com, navigate to the API section, and generate a secret token.

Q: Can I run the server locally for development? A: Yes. Use the development configuration snippet, which runs the server with uv against a local directory.

Q: Is there a published version I can install globally? A: Yes. The published configuration uses uvx to execute the installed package.

Q: What happens if I forget to set the environment variable? A: The server will fail to start or return authentication errors when calling eSignatures endpoints.

mcp-server-esignatures MCP server

MCP server for eSignatures (https://esignatures.com)

Tools

Tool	Category	Description
create_contract	Contracts	Draft for review or send contract
query_contract	Contracts	Retrieve contract info
withdraw_contract	Contracts	Withdraw an unsigned contract
delete_contract	Contracts	Delete a draft or test contract
list_recent_contracts	Contracts	List the recent contracts
create_template	Templates	Create a new contract template
update_template	Templates	Update an existing template
query_template	Templates	Retrieve template content and info
delete_template	Templates	Delete a template
list_templates	Templates	List all your templates
add_template_collaborator	Collaborators	Invite someone to edit a template
remove_template_collaborator	Collaborators	Revoke template editing rights
list_template_collaborators	Collaborators	View who can edit a template

Examples

Creating a Draft Contract

Generate a draft NDA contract for a publisher, which I can review and send. Signer: John Doe, ACME Corp, john@acme.com

Sending a Contract

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

Updating templates

Review my templates for legal compliance, and ask me about updating each one individually

Inviting template collaborators

Invite John Doe to edit the NDA template, email: john@acme.com

Install

Create an eSignatures account

Create an eSignatures account at https://esignatures.com for free, to test the Agent AI by creating templates and sending test contracts.

Claude Desktop

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

Development/Unpublished Servers Configuration

"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"
    ]
  }
}

Published Servers Configuration

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

Authentication

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

eSignatures API Documentation

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

eSignatures Support

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

Contributing

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!