MCP Server for eSignatures
The MCP Server for eSignatures lets you manage electronic signature workflows through:
Contract Management: Create, query, withdraw, delete, and list your recent contracts. You can customize emails, signing order, and multi-factor authentication.
Template Management: Create, update, query, delete, and list reusable contract templates with customizable content including headers, text, and images.
Collaboration: Invite, remove, and list collaborators who can edit templates.
The server requires API secret token authentication to access these features.
Provides tools for eSignatures, enabling creation, management, and processing of digital contracts and templates, including adding collaborators, sending contracts for signature, and retrieving contract information.
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., "@MCP Server for eSignaturessend an NDA contract to John Doe at john@acme.com using my standard template"
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 (Markdown body) |
| Templates | Update an existing template's title/labels |
| Templates | Edit a template's Markdown body via find/replace |
| Templates | Retrieve template metadata |
| Templates | Retrieve a template's Markdown body |
| 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: SMTP MCP Server
Examples
Creating a draft contract
Create a draft NDA for a publisher, ready for me to review and send. Signer: John Doe, ACME Corp, john@acme.com.
Sending a contract from a template
Send an NDA based on my template to John Doe from ACME Corp at john@acme.com. Set the term to 2 years.
Creating a new contract
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.
Editing an existing template
Update my NDA template to include a 12-month non-solicitation clause.
Reviewing templates
Review my templates and suggest improvements. Do not apply any changes until I approve them one by one.
Finding the right template
Find the best template for onboarding a contractor and prepare a draft contract for John Doe.
Managing contracts
Show me the recent contracts that are waiting for signatures.
Updating signer details
Update the signer email on the NDA contract for John Doe to john.doe@acme.com.
Inviting template collaborators
Invite John Doe to edit the NDA template. His email is 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!
Latest Blog Posts
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/esignaturescom/mcp-server-esignatures'
If you have feedback or need assistance with the MCP directory API, please join our Discord server