MCP Server for eSignatures
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESIGNATURES_SECRET_TOKEN | Yes | Your eSignatures API secret token. |
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_contract | 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. |
| query_contract | 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). |
| withdraw_contract | Withdraws a sent contract. |
| delete_contract | Deletes a contract. The contract can only be deleted if it's a test contract or a draft contract. |
| list_recent_contracts | Returns the the details of the latest 100 contracts. |
| create_template | Creates a reusable contract template for contracts to be based on. |
| update_template | Updates the title, labels or the content of a contract template. |
| query_template | 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 |
| delete_template | Deletes a contract template. |
| list_templates | Lists the templates. |