Overview

This MCP (Model Context Protocol) server integrates eSignatures.com functionality into MCP-enabled agents, enabling programmatic drafting, review, and delivery of legally binding contracts and reusable templates. It exposes a focused set of tools that let developer-facing agents create contract drafts, send signature requests, manage templates, and control collaborator access — all via the MCP protocol so AI assistants can act on behalf of users in a controlled, auditable way.

The server is useful for teams automating contract workflows (NDAs, SOWs, MSAs) where an assistant drafts language, populates signer data from context, and either provides a draft for review or sends the agreement for signing. It is built to be configured with an eSignatures API token and run locally (for development) or as a published MCP server.

Features

Draft and send contracts with signer and term metadata
Query contract status and retrieve contract details
Withdraw unsigned contracts or delete drafts/test contracts
Create, update, query, and delete reusable templates
Manage template collaborators (invite/revoke/list editors)
Designed for integration with MCP-enabled agents and toolchains
Simple auth via ESIGNATURES_SECRET_TOKEN environment variable

Installation / Configuration

Create a free eSignatures account and obtain an API secret token: https://esignatures.com
Set the environment variable used by the server:

Bash / macOS / Linux

export ESIGNATURES_SECRET_TOKEN="your-esignatures-api-secret-token"

Windows (PowerShell)

$env:ESIGNATURES_SECRET_TOKEN = "your-esignatures-api-secret-token"

Example MCP client configuration (desktop development). Add a server entry for local or unpublished development:

"mcpServers": {
  "mcp-server-esignatures": {
    "command": "uv",
    "env": {
      "ESIGNATURES_SECRET_TOKEN": "your-esignatures-api-secret-token"
    },
    "args": [
      "--directory",
      "/path/to/mcp-server-esignatures",
      "run",
      "mcp-server-esignatures"
    ]
  }
}

For published deployments (no local directory mount):

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

Start the MCP server per your MCP host/agent instructions. Ensure the ESIGNATURES_SECRET_TOKEN is available to the process.

Available Tools

The server exposes a concise set of MCP tools. Use these from an MCP-capable agent to perform contract and template operations.

Tool	Category	What it does
create_contract	Contracts	Draft a contract (for review) or send it
query_contract	Contracts	Retrieve contract metadata and status
withdraw_contract	Contracts	Withdraw an unsigned/sent contract
delete_contract	Contracts	Delete a draft or test contract
list_recent_contracts	Contracts	List recent contracts for the account
create_template	Templates	Create a new reusable contract template
update_template	Templates	Update an existing template’s content
query_template	Templates	Get template details and content
delete_template	Templates	Remove a template from the account
list_templates	Templates	List all account templates
add_template_collaborator	Collaborators	Invite an editor to a template
remove_template_collaborator	Collaborators	Revoke editor access to a template
list_template_collaborators	Collaborators	List current template editors

For full API shapes and response formats, refer to the upstream eSignatures API docs: https://esignatures.com/docs/api

Use Cases (Concrete Examples)

Create a draft NDA for review:
- Prompt: “Draft an NDA for a publisher: signer John Doe ([email protected]), company ACME Corp. I will review before sending.”
- Tool flow: create_contract → returns draft ID and preview → agent shows draft to user for approval.
Send a contract from a template:
- Prompt: “Send our NDA template to John Doe ([email protected]) with a 2-year term.”
- Tool flow: query or list_templates → create_contract using template ID with signer and term → sends signature request.
Update templates for compliance:
- Prompt: “List my templates and flag any that need legal review based on the new privacy clause.”
- Tool flow: list_templates → query_template for each candidate → agent suggests updates and may call update_template after user approval.
Manage collaborators:
- Prompt: “Invite John Doe ([email protected]) to edit the NDA template.”
- Tool flow: add_template_collaborator → list_template_collaborators to confirm.
Cleanup draft/test contracts:
- Prompt: “List recent contracts and delete any drafts created for testing last week.”
- Tool flow: list_recent_contracts → delete_contract for selected IDs.

Support and Contributing

Source code: https://github.com/esignaturescom/mcp-server-esignatures
API documentation: https://esignatures.com/docs/api
Support: https://esignatures.com/support or [email protected]

Contributions are welcome: open issues for bugs or feature requests, and submit pull requests following the repository guidelines. For major changes, start an issue to discuss the approach.

ESignatures Contract and Template Management for MCP Server