eSignatures MCP Server
Click on "Deploy 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., "@eSignatures MCP Server Send an NDA to John Doe at john@acme.com"
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.
mcp-server-esignatures MCP server
MCP server for eSignatures (https://esignatures.com)
Tools
Tool | Category | Description |
| Contracts | Draft for review or send contract |
| Contracts | Retrieve contract info |
| Contracts | Withdraw an unsigned contract |
| Contracts | Delete a draft or test contract |
| Contracts | List the recent contracts |
| Templates | Create a new contract template |
| Templates | Update an existing template |
| Templates | Retrieve template content and info |
| Templates | Delete a template |
| Templates | List all your templates |
| Collaborators | Invite someone to edit a template |
| Collaborators | Revoke template editing rights |
| Collaborators | View who can edit a template |
Related MCP server: BoldSign MCP Server
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!
Available Tools
13 toolsadd_template_collaboratorC
Creates a HTTPS link for editing a contract template; sends an invitation email if an email is provided..
Inputs: template_id (required), name, email.
create_contractA
Creates a new contract. The contract can be a draft which the user can customize/send, or the contract can be sent instantly. So called 'signature fields' like Name/Date/signature-line must be left out, they are all handled automatically. Contract owners can customize the content by replacing {{placeholder fields}} inside the content, and the signers can fill in Signer fields when they sign the contract.
Inputs: mcp_query (required), contract_source (required), test, title, +14 more.
create_templateB
Creates a reusable contract template for contracts to be based on.
Inputs: title (required), document_elements (required), labels.
delete_contractA
Deletes a contract. The contract can only be deleted if it's a test contract or a draft contract.
Inputs: contract_id (required).
delete_templateA
Deletes a contract template.
Inputs: template_id (required).
list_recent_contractsB
Returns the the details of the latest 100 contracts.
Inputs: no named parameters.
list_template_collaboratorsA
Returns the list of template collaborators, including their GUID, name, email, and the HTTPS link for editing the template
Inputs: template_id (required).
list_templatesB
Lists the templates.
Inputs: no named parameters.
query_contractA
Responds with the contract details, contract_id, status, final PDF url if present, title, labels, metadata, expiry time if present, and signer details with all signer events (signer events are included only for recent contracts, with rate limiting).
Inputs: contract_id (required).
query_templateC
Responds with the template details, template_id, title, labels, created_at, list of the Placeholder fields in the template, list of Signer fields int he template, and the full content inside document_elements
Inputs: template_id (required).
remove_template_collaboratorB
Removes the template collaborator
Inputs: template_id (required), template_collaborator_id (required).
update_templateB
Updates the title, labels or the content of a contract template.
Inputs: title, labels, document_elements.
withdraw_contractC
Withdraws a sent contract.
Inputs: contract_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Each tool targets a distinct resource-action combination: contracts, templates, or template collaborators. Contract lifecycle tools are clearly separated from template tools, and collaborator tools are unambiguous.
Tool names consistently follow a verb_noun pattern (create_contract, query_template, delete_contract). Minor variants like list_recent_contracts and add_template_collaborator still fit the overall convention cleanly.
13 tools is well-scoped for an e-signature server covering contracts, templates, and template collaboration. Each tool has a clear purpose without excessive overlap or bloat.
The server covers contract creation, retrieval, listing, deletion, and withdrawal, plus full template CRUD and collaborator management. Minor gaps exist, such as no explicit update/send contract endpoint or resend/remind capability, but core workflows are supported.
Maintenance
Related MCP Connectors
E-signatures: send, track, remind, void and download envelopes; templates and reports.
E-signature API: send documents for signature, track envelopes, get signed files.
Get PDFs signed: prepare, send and track e-signature requests, then fetch the signed copy.
Read and send documents for signature — templates, recipients, fields and folders.
Related MCP Servers
- AlicenseBqualityBmaintenanceeSignatures.com MCP: full control of contract content from your AI. Read and rewrite contracts and templates as Markdown, before and after sending. Send for signature, manage signers, create public signing links and track status. Hosted with OAuth, no install. Pay-per-use, no subscription.13165 PyPI40MIT
- AlicenseAqualityDmaintenanceEnables interaction with the BoldSign e-signature platform through its API. Supports managing documents, templates, contacts, users, and teams for electronic signature workflows.14MIT
- AlicenseAqualityCmaintenanceEnables Claude to create and manage e-signature contracts, including generating PDFs, sending signing links, and checking contract status.60MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and developers to create, send, and follow up on contracts for e-signature, manage signers and templates, retrieve signed PDFs and audit trails, and verify PDF signatures. It keeps signing and declining in the hands of each signer through personal links.1MIT