BoldSign MCP Server

What is BoldSign MCP Server about?

Enables LLMs to act as agents that can create, retrieve, modify, and control e‑signature resources such as documents, templates, contacts, users, and teams through the BoldSign API.

How to use BoldSign MCP Server?

Obtain a BoldSign API key and (optionally) specify the region (US, EU, CA).\
Set the environment variables BOLDSIGN_API_KEY and BOLDSIGN_API_REGION for the MCP server.\
Add the MCP server configuration to your MCP‑compatible client (Cursor, Windsurf, VS Code, Claude Desktop, Cline, etc.) using the provided JSON snippet.\
Invoke the server’s tools (e.g., list documents, send document from template) from within the LLM client.

Key features of BoldSign MCP Server

Document management: list, retrieve, revoke, and send reminders for documents.\
Template operations: list, retrieve, and generate documents from templates.\
Contact handling: list and retrieve contact details.\
User and team queries: list and retrieve users or teams within an organization.\
Region awareness: supports US, EU, and CA BoldSign regions.

Use cases of BoldSign MCP Server

Automating contract generation and signing workflows directly from an LLM assistant.\
Building a conversational agent that can check document status or send reminders to signers.\
Integrating e‑signature capabilities into custom chat‑based tools without writing API code.\
Providing support staff with AI‑driven access to contact and user directories.

FAQ from the BoldSign MCP Server

Q: Do I need a BoldSign account to use the server?
A: Yes, an account (sandbox or paid) is required to obtain an API key.

Q: Which Node.js version is required?
A: Node.js 18.0.0 or higher.

Q: Can I change the region after setup?
A: Set BOLDSIGN_API_REGION to US, EU, or CA; the default is US.

Q: Which MCP clients are supported?
A: Any client that accepts an MCP server configuration, including Cursor, Windsurf, VS Code, Claude Desktop, and Cline.

Q: Is the server open‑source?
A: Yes, it is licensed under the MIT License.

Author: Syncfusion

Homepage: https://boldsign.com

An MCP server designed to facilitate interaction between Large Language Models (LLMs) and the BoldSign API. The Model Context Protocol (MCP) extends LLM capabilities, enabling them to act as agents when connecting with external systems.

This project contains various tools that interact with the BoldSign API to manage templates and documents for your e-signature.

Prerequisites

Before you begin, ensure you have the following installed and set up:

A BoldSign Account: You will need an account to obtain API credentials. You can sign up for a free trial here or use an existing sandbox or paid account.
BoldSign API Credentials: Obtain your necessary application credentials, specifically an API key. Instructions on how to generate and manage your API key can be found in the BoldSign API documentation.
Node.js: Version 18.0.0 or higher is required.
An MCP Client: To interact with the server, you need an MCP client application. Examples include Cursor, VS Code, Windsurf, Claude Desktop, Cline, or any other compatible MCP client.

Installation

This section provides instructions on how to configure popular MCP clients to connect to the BoldSign MCP server. You will need to add the relevant configuration snippet to your client's settings or configuration file.

Environment Variables

You will need to configure the following environment variables for the BoldSign MCP server to function correctly:

BOLDSIGN_API_KEY - Your API key obtained from your BoldSign account. Please refer to the Prerequisites section for instructions on how to get your API key.
BOLDSIGN_API_REGION - Specifies the region of your BoldSign account. This defaults to US if not specified.
- US for the United States region.
- EU for the Europe region.
- CA for the Canada region.

Install in Cursor

The recommended approach is to add the following configuration to your global Cursor MCP configuration file, typically found at ~/.cursor/mcp.json.

Alternatively, you can install it for a specific project by creating a .cursor/mcp.json file in your project's root folder and adding the same configuration there.

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

Refer to the Cursor MCP documentation for more information on setting up MCP servers in Cursor.

Install in Windsurf

Add the following configuration snippet to your Windsurf MCP configuration file:

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

Refer to the Windsurf MCP documentation for more information on Windsurf MCP setup.

Install in VS Code

Add the following configuration to the VS Code settings file where you manage MCP server configurations:

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

Refer to the VS Code MCP documentation for more information on VS Code MCP setup.

Install in Claude Desktop

Add the following configuration to your Claude Desktop configuration file, which is typically named claude_desktop_config.json:

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

Refer to the Model Context Protocol quickstart guide for more information on Claude Desktop MCP setup.

Install in Cline

Add the following configuration snippet to your Cline MCP configuration file.

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

Refer to the Cline MCP configuration guide for more information on Cline MCP setup.

Available Tools

This MCP server provides access to the following tools via the BoldSign API:

Documents

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

Templates

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

Contacts

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

Users

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

Teams

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

Repository

https://github.com/boldsign/boldsign-mcp

Bug Tracker

https://github.com/boldsign/boldsign-mcp/issues

License

This project is licensed under the MIT License. See the LICENSE file for details.

BoldSign MCP Server