eSignatures MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESIGNATURES_SECRET_TOKEN | Yes | Your eSignatures API secret token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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). |
| withdraw_contractC | Withdraws a sent contract. |
| delete_contractA | Deletes a contract. The contract can only be deleted if it's a test contract or a draft contract. |
| list_recent_contractsB | Returns the the details of the latest 100 contracts. |
| create_templateB | Creates a reusable contract template for contracts to be based on. |
| update_templateB | Updates the title, labels or the content of a contract template. |
| 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 |
| delete_templateA | Deletes a contract template. |
| list_templatesB | Lists the templates. |
| add_template_collaboratorC | Creates a HTTPS link for editing a contract template; sends an invitation email if an email is provided.. |
| remove_template_collaboratorB | Removes the template collaborator |
| list_template_collaboratorsA | Returns the list of template collaborators, including their GUID, name, email, and the HTTPS link for editing the template |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct resource-action combination: contracts, templates, or template collaborators. Contract lifecycle tools are clearly separated from template tools, and collaborator tools are unambiguous.
Tool names consistently follow a verb_noun pattern (create_contract, query_template, delete_contract). Minor variants like list_recent_contracts and add_template_collaborator still fit the overall convention cleanly.
13 tools is well-scoped for an e-signature server covering contracts, templates, and template collaboration. Each tool has a clear purpose without excessive overlap or bloat.
The server covers contract creation, retrieval, listing, deletion, and withdrawal, plus full template CRUD and collaborator management. Minor gaps exist, such as no explicit update/send contract endpoint or resend/remind capability, but core workflows are supported.