This MCP server integrates with the eSignatures platform to manage contracts, templates, and collaborators via a set of defined tools. The server exposes contract operations (create, query, withdraw, delete, and list recent contracts), template operations (create, update, query, delete, and list templates), and collaboration controls (add, remove, and list template collaborators). You can invoke these tools through the MCP interface to automate contract workflows such as drafting NDA contracts, sending templates to signers, and managing template access for team members. The server relies on an environment token (ESIGNATURES_SECRET_TOKEN) to authenticate with the eSignatures API, so ensure this token is securely configured when running the server.

Prerequisites:

• Python 3.9+ installed on your system
• Access to the eSignatures API and a valid ESIGNATURES_SECRET_TOKEN
• MCP runtime environment (the uv/uvx tools) available on your system

Installation steps:

1. Ensure Python is installed. Verify: python3 --version
2. Obtain and export your eSignatures secret token: export ESIGNATURES_SECRET_TOKEN=your-esignatures-api-secret-token
3. Install and run the MCP server using uvx (Python-based MCP runner):

   If you have the MCP server package available locally or via a registry, follow your usual install flow.

   Example run (from repository root or configured path):

   uvx run mcp-server-esignatures
4. If you are using a development configuration, ensure your local paths are correctly set and the server name matches the config: "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" ] } }

Notes:

• The published setup uses uvx with the server name and requires ESIGNATURES_SECRET_TOKEN to be set.
• If you prefer development mode, you may switch to the uv-based command and supply the local directory path.

Environment variables and configuration tips:

• ESIGNATURES_SECRET_TOKEN is required to authenticate with the eSignatures API.
• Keep your secret token secure; do not commit it to version control.
• When running in production, prefer the published uvx configuration to ensure consistent startup behavior.
• If you encounter authentication errors, verify token validity and check the eSignatures API status page.
• The MCP server exposes a suite of contract, template, and collaborator tools; consult the eSignatures API docs for endpoint details and rate limits.