eSignatures MCP

How to Install and Use eSignatures MCP

If you want to manage and send contracts easily, eSignatures MCP (MCP server for eSignatures) is a great tool. It helps you create, send, update, and manage contracts and templates using simple commands. In this guide, we’ll walk you through how to install eSignatures MCP and show you some basic examples of how to use its features.

Step 1: Create an eSignatures Account

Before you start using eSignatures MCP, you need to create a free account on https://esignatures.com. This lets you test the software by creating templates and sending contracts.

• Visit the website.
• Sign up for a free account.
• Once registered, get your API secret token from your account settings. You will need this token to connect the MCP server to your eSignatures account.

Step 2: Configure Your Environment for eSignatures MCP

Next, you must set up your environment so that the MCP server knows your secret token.

• Set the environment variable ESIGNATURES_SECRET_TOKEN with your secret token. For example, on many systems, you can run:

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

This sets the token temporarily in the current terminal. Make sure you replace "your-esignatures-api-secret-token" with the token you got from your eSignatures account.

Step 3: Set Up the MCP Server on Your Machine

Now, you can set up the eSignatures MCP server locally for development or testing.

If you want to run it locally (for example, on Mac or Windows), you should add the following configuration to the Claude Desktop app config file (assuming you are using Claude to run MCP servers):

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

Make sure to update the directory to where you have downloaded or cloned the MCP server files.

Step 4: Running the MCP Server (Published Version)

If you want to run the published server version instead of local development, use this configuration:

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

This will run the MCP server from the published source, using your API token.

Step 5: Using eSignatures MCP Tools

Once installed and running, you can use the eSignatures MCP tools, which include commands to create contracts, update templates, add collaborators, and more.

Here are some examples to get you started:

• Creating a Draft Contract

Write a command like this to generate a draft contract for review:

Generate a draft NDA contract for a publisher, which I can review and send. Signer: John Doe, ACME Corp, [email protected]

• Sending a Contract

To send a contract based on a template, you might say:

Send an NDA based on my template to John Doe, ACME Corp, [email protected]. Set the term to 2 years.

• Updating Templates

Ask the MCP to check your templates and suggest updates:

Review my templates for legal compliance, and ask me about updating each one individually

• Inviting Template Collaborators

Invite a person to edit a template by saying:

Invite John Doe to edit the NDA template, email: [email protected]

Summary

To install and use eSignatures MCP:

1. Create a free account at eSignatures.com.
2. Set your ESIGNATURES_SECRET_TOKEN environment variable.
3. Configure and run the MCP server locally or as published.
4. Use simple commands to create, send, and manage contracts and templates.

With this setup, eSignatures MCP makes handling electronic signatures and contract templates straightforward and effective.