eSignatures

This MCP server connects to the eSignatures API to manage contracts and templates. It exposes a set of endpoints you can use from an MCP client to create, query, update, and collaborate on contracts and templates, enabling streamlined eSignature workflows.

How to use

You interact with this MCP server through an MCP client to draft contracts, manage templates, and invite collaborators. Use the available tools to create contracts or templates, then send, review, or withdraw drafts as needed. You can also invite collaborators to edit templates and review contract information, all within a unified MCP interface.

How to install

Prerequisites
- A functional runtime for your chosen MCP runner (uv/uvx) installed on your machine.
- An eSignatures account and an API secret token to authorize API calls.
- Basic familiarity with environment variables and command-line usage.

1) Create an eSignatures account for testing if you don’t have one yet. This lets you test templates and contracts in a sandbox style workflow.
2) Obtain your ESIGNATURES_SECRET_TOKEN from your eSignatures account. You will set this as an environment variable to authenticate all requests.
3) Start the MCP server in development mode
- For development/unpublished servers use the following configuration. This runs locally from your directory and registers the MCP server under the name mcp-server-esignatures:

"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" ] } }

4) Start the MCP server in published/production mode
- Use the published servers configuration to run the MCP server via uvx:

"mcpServers": { "mcp-server-esignatures": { "command": "uvx", "args": [ "mcp-server-esignatures" ], "env": { "ESIGNATURES_SECRET_TOKEN": "your-esignatures-api-secret-token" } } }

5) Set the environment variable in your shell before starting if you run the server outside of the config file:
- For Unix-like shells:
  - export ESIGNATURES_SECRET_TOKEN=your-esignatures-api-secret-token
- For Windows PowerShell:
  - $env:ESIGNATURES_SECRET_TOKEN = "your-esignatures-api-secret-token"
6) Verify connectivity and try basic actions using your MCP client, such as creating a draft contract or listing templates.

Configuration and security

Environment variable you must set:

• ESIGNATURES_SECRET_TOKEN: Your eSignatures API secret token. This authenticates API requests from the MCP server.

Available tools and how to use them

Tools include the following actions you can perform through your MCP client. Each tool is used to manage different aspects of contracts and templates.

Examples

Draft a contract for review or sending, set up templates, and invite collaborators to templates as shown in the usage examples.

Troubleshooting and notes

If you encounter authentication issues, double-check that ESIGNATURES_SECRET_TOKEN is correctly set in the environment where the MCP server runs. Ensure your token has the necessary permissions for the actions you are trying to perform.

Available tools

create_contract

Draft for review or send contract

query_contract

Retrieve contract info

withdraw_contract

Withdraw an unsigned contract

delete_contract

Delete a draft or test contract

list_recent_contracts

List the recent contracts

create_template

Create a new contract template

update_template

Update an existing template

query_template

Retrieve template content and info

delete_template

Delete a template

list_templates

List all your templates

add_template_collaborator

Invite someone to edit a template

remove_template_collaborator

Revoke template editing rights

list_template_collaborators

View who can edit a template