MCP Server for eSignatures. com
mcp-server-esignatures Servidor MCP
Servidor MCP para firmas electrónicas ( https://esignatures.com )
Herramientas
Herramienta | Categoría | Descripción |
| Contratos | Borrador para revisión o envío de contrato |
| Contratos | Recuperar información del contrato |
| Contratos | Retirar un contrato no firmado |
| Contratos | Eliminar un borrador o contrato de prueba |
| Contratos | Enumere los contratos recientes |
| Plantillas | Crear una nueva plantilla de contrato |
| Plantillas | Actualizar una plantilla existente |
| Plantillas | Recuperar contenido e información de la plantilla |
| Plantillas | Eliminar una plantilla |
| Plantillas | Enumere todas sus plantillas |
| Colaboradores | Invitar a alguien a editar una plantilla |
| Colaboradores | Revocar los derechos de edición de plantillas |
| Colaboradores | Ver quién puede editar una plantilla |
Related MCP server: CanUSign MCP Server
Ejemplos
Creación de un borrador de contrato
Generate a draft NDA contract for a publisher, which I can review and send. Signer: John Doe, ACME Corp, john@acme.com
Envío de un contrato
Send an NDA based on my template to John Doe, ACME Corp, john@acme.com. Set the term to 2 years.
Actualización de plantillas
Review my templates for legal compliance, and ask me about updating each one individually
Invitar a colaboradores de plantillas
Invite John Doe to edit the NDA template, email: john@acme.com
Instalar
Crear una cuenta de firmas electrónicas
Cree una cuenta de eSignatures en https://esignatures.com de forma gratuita para probar el Agente AI creando plantillas y enviando contratos de prueba.
Escritorio de Claude
En MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json En Windows: %APPDATA%/Claude/claude_desktop_config.json
Configuración de servidores no publicados/desarrollo
"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"
]
}
}Configuración de servidores publicados
"mcpServers": {
"mcp-server-esignatures": {
"command": "uvx",
"args": [
"mcp-server-esignatures"
],
"env": {
"ESIGNATURES_SECRET_TOKEN": "your-esignatures-api-secret-token"
}
}
}Autenticación
Para utilizar este servidor, debe configurar la variable de entorno ESIGNATURES_SECRET_TOKEN con su token secreto de API de firmas electrónicas.
Documentación de la API de firmas electrónicas
Para obtener una guía detallada sobre los puntos finales, parámetros y respuestas de la API, consulte API de firmas electrónicas .
Soporte para firmas electrónicas
Para obtener ayuda, navegue hasta Soporte o comuníquese con support@esignatures.com .
Contribuyendo
¡Agradecemos sus contribuciones! Si desea colaborar, por favor, bifurque el repositorio y haga los cambios que considere oportunos. Aquí tiene algunas pautas:
Informes de errores : abra un problema para informar cualquier error que encuentre.
Solicitudes de funciones : sugiera nuevas funciones abriendo un problema con la etiqueta "mejora".
Solicitudes de extracción : asegúrese de que su solicitud de extracción siga el estilo del código existente.
Documentación : Ayude a mejorar o traducir la documentación. Se agradece cualquier mejora.
Para cambios importantes, por favor, primero abre una publicación para comentar qué te gustaría cambiar. ¡Esperamos tus contribuciones!
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: contract_source (required), mcp_query (required), template_id, 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 has a clearly distinct purpose targeting specific resources and actions, such as create_contract vs. withdraw_contract for contracts, and create_template vs. update_template for templates. There is no overlap or ambiguity in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun naming pattern, such as create_contract, delete_template, and list_recent_contracts. The naming is uniform throughout, with no deviations in style or convention, enhancing readability and predictability.
With 13 tools, the server is well-scoped for eSignatures, covering core operations like contract and template management, collaboration, and querying. Each tool serves a distinct and necessary function without being excessive or insufficient for the domain.
The tool set provides comprehensive CRUD and lifecycle coverage for contracts and templates, including collaboration features. Minor gaps exist, such as no direct tool for updating contract details or handling signer-specific actions beyond querying, but agents can likely work around these with the available tools.
Maintenance
Related MCP Connectors
Make contracts from templates, send them for e-signature by email, and track who has signed.
Make contracts from templates, send them for e-signature by email, and track who has signed.
Send, track, and manage documents for eSignature: templates, drafts, signing status, signed PDFs.
Send documents for legally binding e-signature and manage the reusable templates behind them.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables managing electronic signatures and contracts through the eSignatures API, including creating, sending, and withdrawing contracts, as well as managing templates and collaborators.13MIT
- AlicenseAqualityCmaintenanceEnables Claude to create and manage e-signature contracts, including generating PDFs, sending signing links, and checking contract status.60MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and manage contract templates, draft agreements by filling in template variables and signers, send documents out for legally binding e-signature, and track signer status as signatures come in. It runs as a hosted remote server, so there is nothing to install or self-host.MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to query, create, and manage contracts in plain English from any MCP client, including drafting and sending agreements, tracking renewals and signers, and building templates. It supports OAuth-authenticated workflows with safe defaults such as creating drafts and confirming before sending or changing live agreements.MIT