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 アカウントを無料で作成し、テンプレートを作成してテスト契約を送信することでエージェント 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"
}
}
}認証
このサーバーを使用するには、eSignatures API シークレット トークンを使用してESIGNATURES_SECRET_TOKEN環境変数を設定する必要があります。
電子署名 API ドキュメント
API エンドポイント、パラメーター、応答の詳細なガイドについては、 eSignatures APIを参照してください。
電子署名サポート
サポートについては、 「サポート」にアクセスするか、 support@esignatures.comにお問い合わせください。
貢献
貢献を歓迎します!貢献したい場合は、リポジトリをフォークして、必要に応じて変更を加えてください。ガイドラインは以下のとおりです。
バグレポート: 発生したバグを報告するには、問題を開いてください。
機能リクエスト: 「機能強化」ラベルを付けて問題を開いて、新しい機能を提案します。
プル リクエスト: プル リクエストが既存のコード スタイルに従っていることを確認します。
ドキュメント: ドキュメントの改善や翻訳にご協力ください。ドキュメントの改善はどんな形でも歓迎します。
大きな変更については、まず問題を作成して、変更したい点についてご相談ください。皆様のご協力をお待ちしております。
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