boldsign

This BoldSign MCP Server acts as a bridge between large language models (LLMs) and the BoldSign API, exposing a set of tools to manage documents, templates, contacts, users, and teams within your BoldSign account. The server provides programmatic access to common BoldSign tasks such as listing documents and templates, sending documents from templates, retrieving document details and statuses, revoking documents in progress, sending reminders to signers, and managing contacts, users, and teams. You can invoke these tools from an MCP client (for example Cursor, Windsurf, VS Code, Claude Desktop, or Cline) and pass natural language prompts that map to specific API actions. Ensure your MCP client is configured to connect to the boldsign MCP server using the provided configuration snippet and your BoldSign API credentials.

Key capabilities include:

• Documents: list documents, list team documents, get document details/status, revoke a document, send reminders to signers.
• Templates: list templates, get template details, create and send a document from a template.
• Contacts: list contacts, get contact details.
• Users: list users, get user details.
• Teams: list teams, get team details.

To use the tools, configure your MCP client with the boldsign server (see installation instructions) and provide your BoldSign API key and region as environment variables. Then, within your prompts, reference the available endpoints (e.g., list documents, get template details) as actions your LLM can perform against the BoldSign API.

Prerequisites

• Node.js v18.0.0 or higher
• A BoldSign account with API access and a valid API key
• An MCP client (examples: Cursor, Windsurf, VS Code, Claude Desktop, Cline) to connect to the MCP server

Step 1: Obtain API credentials

• Sign up for a BoldSign account or use an existing account.
• Generate an API key from the BoldSign API credentials section as documented by BoldSign.

Step 2: Install and run the MCP server configuration

• This server is exposed via the npm package @boldsign/mcp and can be run using npx. The recommended configuration for MCP clients is shown below. Ensure you replace YOUR_BOLDSIGN_API_KEY with your actual API key.

Step 3: Configure your MCP client

• Copy one of the following configuration snippets into your MCP client configuration (Cursor Windsurf VS Code Claude Desktop Cline), replacing the API key with your own.

Cursor (global ~/.cursor/mcp.json or project-local):

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

Windsurf:

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

VS Code settings snippet:

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

Claude Desktop / Cline snippets follow the same pattern: replace with your actual API key and region, and point to the same npm package.

Step 4: Run a quick test

• After configuring, start the MCP client and ensure the boldsign server appears in your MCP client’s server list. Use a simple prompt to list documents or templates to verify connectivity against BoldSign APIs.

Tips and common issues:

• Ensure BOLDSIGN_API_KEY is kept secret and not committed to version control.
• Region defaults to US if not specified; set BOLDSIGN_API_REGION to US, EU, or CA as needed.
• Check BoldSign API rate limits in case of high-frequency requests from LLM prompts.
• If you encounter authentication errors, double-check that the API key has the necessary permissions for the requested endpoints.
• The available endpoints mirror BoldSign API capabilities for documents, templates, contacts, users, and teams; refer to BoldSign API docs for specific parameters and pagination handling.
• When upgrading the MCP server package, verify compatibility with your MCP client configuration, especially environment variable names.