BoldSign Assistant MCP Server

Overview

The BoldSign Assistant is a specialized Model Context Protocol (MCP) server designed to simplify working with the BoldSign API. It integrates seamlessly with MCP-compatible clients, providing intelligent guidance that makes electronic signature workflows faster and easier.

Key Features

• Intelligent document preparation and signature workflow automation
• Detailed guidance on BoldSign API usage and integration

How It Helps

The BoldSign Assistant helps you with BoldSign eSignature API integration questions and provides documentation references. This tool is useful when you need assistance with:

• Understanding specific BoldSign API endpoints such as:
  • Signature Requests
  • Templates
  • Audit Logs
  • Reminders
  • Access Codes
  • Webhooks
• Implementation techniques for:
  • Sending documents
  • Managing signers
  • Retrieving signed files using BoldSign

Provide your detailed question in the query parameter. When your question involves specific BoldSign API features, the assistant detects those references and retrieves relevant documentation and guidance.

Note: This MCP server provides guidance, documentation references, and implementation advice. It does not execute BoldSign API calls or perform actions on your account.

Prerequisites

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

1. 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.
2. 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.
3. Node.js: Version 18.0.0 or higher is required.
4. 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 Assistant 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 Assistant 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 – United States region
  • EU – Europe region
  • CA – Canada region
  • AU – Australia region

Quick Start

1. Configure the MCP server in your client (see Installation).
2. Restart your MCP client.
3. Open a new chat and type: @boldsign How do I send a document for signature using the BoldSign API?

The assistant will respond with relevant documentation and implementation guidance.

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-assistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@boldsign/assistant"],
      "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-assistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@boldsign/assistant"],
      "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-assistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@boldsign/assistant"],
      "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-assistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@boldsign/assistant"],
      "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-assistant": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@boldsign/assistant"],
      "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.

Usage

To activate the BoldSign Assistant MCP server:

• Start your prompt with one of the following:
  • BoldSignAssistant
  • /boldsign-assistant
  • /boldsign
  • @boldsign
  • @ask_boldsign
• In VS Code, use #BoldSignAssistant for direct invocation.
• Grant permission for the server to run (for the session, workspace, or always).
• For best results, start a new chat for each new topic to maintain clean context.

Mode Availability

BoldSign Assistant MCP Server provides full access to all AI interaction modes — Ask/Chat, Edit, and Agent — across supported MCP clients.

Best Practices for Effective Usage

• Be specific: Mention both platform and workflow (e.g., "How do I send a BoldSign document with multiple signers?").
• Provide context: Include details about your use case for more targeted solutions.
• Use descriptive queries: Avoid vague questions that lack necessary context.
• Start fresh for new topics: Begin a new chat session when switching workflows or topics.

Example Queries

• "Where can I find the API reference for sending a document for signature?"
• "How do I integrate BoldSign API with my Node.js application?"
• "Documentation on setting up webhooks to track when a document is signed?"

Troubleshooting

If you encounter issues:

• Verify your API key is correctly configured.
• Ensure the MCP server is enabled in your client’s tools selection.
• Check that you’re using a compatible MCP client version.
• Try restarting your development environment.

Support

Product support is available through the following mediums:

• Support ticket – Guaranteed response in 24 hours, unlimited tickets, holiday support
• Request feature or report bug
• Live chat

License

This is a commercial product and requires a paid license for possession or use. Syncfusion® licensed software, including this component, is subject to the BoldSign terms and use. To acquire a license, you can purchase here or test your integration with full API access in a free sandbox.

© 2025 BoldSign, a Syncfusion product. All Rights Reserved.