Boldsign MCP

What boldsign/boldsign-mcp does

The boldsign/boldsign-mcp MCP server lets an MCP-compatible application call selected BoldSign API operations through an agent interface. Its coverage is centered on e-signature administration: documents, templates, contacts, users, and teams.

For documents, it can retrieve paginated account or team listings, inspect a document's details and status, revoke an in-progress document, and send reminders to signers who have not completed their signatures. Template operations include listing templates, retrieving a template, and creating and sending a signing document from a configured template.

The server also exposes read operations for contacts, organization users, and teams. These operations retrieve lists or details by identifier rather than creating or modifying those records.

How it works

The project is a local MCP server launched with Node.js. An MCP client starts the server as a stdio process, and the server uses the supplied BoldSign credentials to call the BoldSign API. The README lists Cursor, Windsurf, VS Code, Claude Desktop, and Cline as compatible client options.

The BoldSign account region is configurable. Supported values are US, EU, and CA; US is the default when no region is supplied. API responses and available operations depend on the connected BoldSign account and the API endpoints used by each tool.

Setup and configuration

Using the boldsign/boldsign-mcp MCP server requires a BoldSign account, an API key, Node.js 18 or later, and an MCP client. The local configuration uses the npm package @boldsign/mcp and runs it with npx.

Set these environment variables in the client configuration:

• BOLDSIGN_API_KEY: The API key generated in the BoldSign account.
• BOLDSIGN_API_REGION: The account region, using US, EU, or CA. If omitted, the server uses US.

For example, a stdio client configuration uses npx with -y @boldsign/mcp as its arguments. The exact configuration file depends on the client. Cursor uses an MCP JSON file, while Claude Desktop uses claude_desktop_config.json; the README provides equivalent examples for the other listed clients.

Tools and capabilities

Available capabilities are grouped by BoldSign resource:

• Documents: list account documents, list team documents, get document details and status, revoke an in-progress document, and send signer reminders.
• Templates: list templates, get template details, and send a document from a template.
• Contacts: list contacts and retrieve contact details.
• Users: list organization users and retrieve user details.
• Teams: list organization teams and retrieve team details.

Document and template listing operations are paginated according to the corresponding BoldSign API endpoints.

Limitations and notes

The boldsign/boldsign-mcp MCP server repository is marked deprecated. The maintainers point users to the hosted BoldSign MCP Server for improved authentication options, additional features, and a fully managed deployment. This repository's setup therefore applies to the local npm-based server described in its README, not necessarily to the hosted replacement.

A BoldSign API credential is required, so this server is not credential-free. The README describes using a free trial, sandbox account, or paid account to obtain access, but it does not specify API limits or pricing for the individual operations. The listed tools also focus on the resources and actions documented above; no document upload, signing completion, webhook, or record-creation tool is described.

Getting started with this boldsign/boldsign-mcp MCP server

Always refer to the official documentation for the most accurate and up-to-date information.