Introducing BoldSign MCP Server: Your AI Assistant for eSignatures

Looking to bring AI-powered automation into your eSignature workflows? Meet the BoldSign MCP– it lets your AI tools interact with BoldSign’s eSignature APIs using natural-language commands.

Imagine telling your AI assistant, “Send the NDA to John,” and it just does it. No clicking through templates, no hunting for email addresses, no manual follow-ups.

That’s the power of the BoldSign MCP Server —tool that connects MCP clients (like GitHub Copilot, Claude Desktop, Cline) directly to the BoldSign eSignature API.

It’s built to help you automate document workflows using natural language. Whether you’re managing contracts, onboarding new hires, or sending compliance forms, the BoldSign MCP Server makes it easy to get things done — fast, smart, and hands-free.

What is the BoldSign MCP Server?

The BoldSign MCP Server acts as a bridge between MCP clients and the BoldSign eSignature platform. It enables natural language commands to be translated into API calls that manage documents, templates, contacts, and more.

MCP clients — such as Cursor, Visual Studio Code (with MCP support), Windsurf, Claude Desktop, Cline — connect to the MCP Server to perform tasks like sending contracts, retrieving templates, or checking document status. This setup allows users to interact with BoldSign using simple, intuitive language.

How it Works

The BoldSign MCP Server is built on the Model Context Protocol (MCP), which defines how clients and servers communicate.

Here’s how it works:

• An MCP client sends a request to the MCP Server.
• The server interprets the request and interacts with the BoldSign API.
• The result is sent back to the client, completing the task.

This architecture allows for seamless automation of eSignature workflows through natural language interfaces.

Real-life Example

Let’s say you type: “Send NDA Agreement to Mathew Wilson.”

• The MCP Server locates the ‘NDA Agreement ‘ template.
• It retrieves Mathew Wilson’s email from your contact list.
• It sends the document for signature.
• You receive a confirmation: “The NDA Agreement has been successfully sent to Mathew Wilson ([email protected]).” Including signer details and documentID.

Need to follow up or send a reminder? Just ask your MCP client.

Available Tools

The BoldSign MCP Server provides access to a comprehensive set of tools via the BoldSign API:

Documents 

1. List documents: Retrieves a paginated list of your documents. 
2. List team documents: Retrieves a paginated list of team documents.��
3. Get document: Retrieves detailed information, including status, for a specific document using its ID. 
4. Revoke document: Allows you to cancel or call off a document that is in progress. 
5. Send reminders: Sends reminders to signers who have not yet completed their signature on a document. 

Templates

6. List templates: Retrieves a paginated list of templates available in your BoldSign account. 
7. Get template: Retrieves detailed information for a specific template using its ID. 
8. Send document from template: Creates and sends out a document for signing based on a pre-configured template. 

Contacts 

9. List Contacts: Retrieves a paginated list of contacts from your BoldSign account. 
10. Get Contact: Retrieves detailed information for a specific contact using their ID. 

Users 

11. List Users: Retrieves a paginated list of users in your BoldSign organization. 
12. Get User: Retrieves detailed information for a specific user using their ID. 

Teams 

13. List Teams: Retrieves a paginated list of teams in your BoldSign organization. 
14. Get Team: Retrieves detailed information for a specific team using their ID. 

Why it Matters

If you’re handling contracts, onboarding, or compliance — the BoldSign MCP Server is a game-changer. It helps automate repetitive tasks, reduce errors, and accelerate workflows, all while keeping the process simple and intuitive.

By leveraging MCP clients, organizations can unlock the full potential of AI-driven eSignature automation.

Getting Started with the BoldSign MCP Server 

To start using the BoldSign MCP Server, you’ll need to set it up and connect it with both your BoldSign account and an MCP-compatible client. Here’s a step-by-step guide to help you get started:

Prerequisites 

• BoldSign Account: Sign up for a free trial or use an existing sandbox/paid account to obtain API credentials. Sign up here. 
• BoldSign API Key: Generate an API key from the BoldSign web app. Refer to the BoldSign API documentation for instructions. 
• Node.js: Install Node.js (version 18.0.0 or higher). 
• MCP-Compatible Client:

Choose an MCP-compatible app to interact with the server. Some popular options include:

• Cursor
• Visual Studio Code (with MCP support)
• Windsurf
• Claude Desktop
• Cline
• Or any other app that supports the Model Context Protocol

Setup Instructions in Claude Desktop:

Download and install the latest version of Claude Desktop from the official website https://claude.ai/download.

Installation

This section assumes that you have already installed the Claude Desktop application and signed in with your account.

1. In Claude Desktop, open the Settings menu in the bottom-left corner.

2. In the Settings page, select the Developers tab.

3. Next, click on the Edit config button to open the claude_desktop_config.json file in your preferred text editor.

4. Add the following configuration to claude_desktop_config.json:

{
    "mcpServers": {
        "boldsign": {
            "command": "npx",
            "args": ["-y", "@boldsign/mcp"],
            "env": {
                "BOLDSIGN_API_KEY": "YOUR_BOLDSIGN_API_KEY",
                "BOLDSIGN_API_REGION": "US"
            }
        }
    }
}

Replace YOUR_BOLDSIGN_API_KEY with your actual BoldSign API key. The BOLDSIGN_API_REGION can be set to US, EU, or CA depending on your account region.

5. Save your changes, quit Claude Desktop, and restart the application to apply them.
6. Once the application is restarted, you should see the BoldSign MCP server tools listed in the Search and tools section.

For installation in other MCP Clients, you can check the documentation below 

Setup BoldSign MCP server in Cursor

Setup BoldSign MCP Server in Windsurf

Setup BoldSign MCP Server in VS Code

Setup BoldSign MCP Server in Cline

Conclusion 

The BoldSign MCP Server is a game-changer for businesses looking to combine the power of AI with eSignature capabilities. By connecting LLMs with BoldSign’s API, it enables developers and organizations to automate and optimize their document workflows like never before.  

Ready to get started? Sign up for a free BoldSign account, set up the MCP server, and experience the future of eSignature automation today! For more details, visit the BoldSign MCP GitHub repository and explore the BoldSign API documentation. 

We value your feedback! Feel free to share your thoughts or comments in the section below. 

Need help or have questions? Our support team is here for you—visit the Support portal to get assistance. 

Evans Omondi Otieno

Technical Assistant

Evans Omondi Otieno is a customer support representative and writer at BoldSign, specializing in creating clear, insightful content to help users navigate eSignature solutions. As a blog author, Evans writes well-researched articles that simplify technical concepts, helping businesses and professionals understand how to use BoldSign effectively. With expertise in technical support and content creation, he ensures users have a seamless experience and gain valuable knowledge from his articles.