MCP Server for eSignatures. com
mcp-server-esignatures MCP 服务器
电子签名的 MCP 服务器( https://esignatures.com )
工具
工具 | 类别 | 描述 |
| 合同 | 起草以供审查或发送合同 |
| 合同 | 检索合同信息 |
| 合同 | 撤回未签署的合同 |
| 合同 | 删除草稿或测试合同 |
| 合同 | 列出最近的合同 |
| 模板 | 创建新的合同模板 |
| 模板 | 更新现有模板 |
| 模板 | 检索模板内容和信息 |
| 模板 | 删除模板 |
| 模板 | 列出所有模板 |
| 合作者 | 邀请某人编辑模板 |
| 合作者 | 撤销模板编辑权限 |
| 合作者 | 查看谁可以编辑模板 |
Related MCP server: CanUSign MCP Server
示例
创建合同草案
Generate a draft NDA contract for a publisher, which I can review and send. Signer: John Doe, ACME Corp, john@acme.com
发送合同
Send an NDA based on my template to John Doe, ACME Corp, john@acme.com. Set the term to 2 years.
更新模板
Review my templates for legal compliance, and ask me about updating each one individually
邀请模板合作者
Invite John Doe to edit the NDA template, email: john@acme.com
安装
创建电子签名帐户
在https://esignatures.com免费创建一个 eSignatures 帐户,通过创建模板和发送测试合同来测试 Agent AI。
克劳德桌面
在 MacOS 上: ~/Library/Application\ Support/Claude/claude_desktop_config.json在 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"
}
}
}验证
要使用此服务器,您需要使用您的电子签名 API 秘密令牌设置ESIGNATURES_SECRET_TOKEN环境变量。
电子签名 API 文档
有关 API 端点、参数和响应的详细指南,请参阅电子签名 API 。
电子签名支持
如需支持,请导航至支持或联系support@esignatures.com 。
贡献
欢迎贡献!如果您愿意贡献代码,请 fork 代码库并根据需要进行修改。以下是一些准则:
错误报告:请打开问题来报告您遇到的任何错误。
功能请求:通过打开带有“增强”标签的问题来建议新功能。
拉取请求:确保您的拉取请求遵循现有的代码样式。
文档:帮助改进或翻译文档。任何形式的文档改进都将受到赞赏。
对于重大变更,请先提交一个 issue 来讨论您想要修改的内容。我们期待您的贡献!
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