BoldSign MCP Server: Search, Request & Manage E-Signatures

Overview

BoldSign MCP Server is a Model Context Protocol (MCP) adapter that connects LLM-based agents and MCP-compatible clients to the BoldSign e-signature API. It exposes common e-signature operations over the MCP protocol so developer tools (Cursor, VS Code, Windsurf, Claude Desktop, etc.) and LLMs can search, request, and manage contracts programmatically from conversational or editor-based workflows.

The server is useful when you want to extend an assistant or automation pipeline with real-world e-signature capabilities—search for agreements, fetch document status, send reminders, or revoke in-progress documents—without embedding BoldSign credentials or HTTP logic into the client. It runs as a local MCP server (stdio) and communicates with BoldSign using your API key and region.

Features

• MCP protocol bridge for BoldSign API (works with MCP clients & LLMs)
• Document operations: list, get details, send reminders, revoke
• Template operations: list and get template details
• Paginated list retrieval for large accounts
• Region-aware API calls (US / EU / CA)
• Simple deployment via npx (no global install required)

Prerequisites

• BoldSign account and API key (see BoldSign developer docs)
• Node.js 18.0.0 or later
• An MCP-compatible client (Cursor, VS Code, Windsurf, Claude Desktop, Cline, etc.)

Installation / Configuration

You can run the server directly or register it in your MCP client configuration. The package is published on npm as @boldsign/mcp; the server is typically launched via npx so you don’t need to install it globally.

Environment variables

# Required
export BOLDSIGN_API_KEY="your_api_key_here"

# Optional (defaults to US)
export BOLDSIGN_API_REGION="US"  # values: US, EU, CA

Run locally (quick test)

BOLDSIGN_API_KEY="sk_..." BOLDSIGN_API_REGION="US" npx -y @boldsign/mcp

Cursor config (add to ~/.cursor/mcp.json or .cursor/mcp.json in project)

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

VS Code config (add in MCP servers settings)

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

(Use a similar block for Windsurf, Claude Desktop, Cline—same command/args/env pattern.)

Environment variables reference:

Available Tools / Resources

The MCP server maps to key BoldSign API endpoints. Primary tools exposed:

• Documents
  • List documents (paginated)
  • List team documents (paginated)
  • Get document details & status
  • Revoke/cancel a document in progress
  • Send reminders to pending signers
• Templates
  • List templates (paginated)
  • Get template details

Helpful links:

• GitHub repo: https://github.com/boldsign/boldsign-mcp
• BoldSign API docs: https://developers.boldsign.com

Use Cases

1. Search for a contract and fetch status

   • Agent queries the MCP server for documents matching a signer name or subject.
   • Server returns a paginated list and the agent requests details for a selected document to determine completion status.

2. Send a reminder to pending signers

   • From a chat or IDE, ask the assistant: “Send a reminder for contract ID abc123 to the remaining signers.”
   • The assistant calls the MCP tool to trigger BoldSign’s send-reminder endpoint, then confirms success to the user.

3. Revoke a document that was sent by mistake

   • When a document is in-flight and needs to be canceled, the agent invokes revoke on the document ID to halt the signing flow.

4. Inspect templates for building a new agreement

   • Query template list, select the appropriate template, fetch field definitions and roles to programmatically prepare a new document or draft request.

Quick Tips

• Keep your API key private; prefer running the MCP server locally or behind secure runtime secrets.
• Use pagination when listing documents/templates to avoid truncation on large accounts.
• The MCP server is stateless relative to BoldSign data—operations reflect the current state in your BoldSign account.

For full source, issues and contributions, visit the repository: https://github.com/boldsign/boldsign-mcp.