SuperAPI AI Directory
Partner with us中文AI newsFavorites
All toolsAI developer platformsboldsign-mcp

boldsign-mcp

Search, request and manage e-signature contracts with BoldSign.

Open website

About this tool

Purpose

BoldSign MCP Server is a Model Context Protocol (MCP) server used to facilitate interaction between large language models (LLMs) and the BoldSign API. MCP extends the capabilities of LLMs, enabling them to act as agents when connecting to external systems. This project includes multiple tools for managing e-signature-related templates and documents through the BoldSign API.

Author: Syncfusion; Homepage:https://boldsign.com；仓库地址：https://github.com/boldsign/boldsign-mcp。

Important: This repository is deprecated. For improved authentication options, more features, and a fully managed experience, please use the hosted BoldSign MCP Server.

Key Capabilities

This MCP server provides the following tools through the BoldSign API:

  • List documents: Retrieve a paginated list of documents.
  • List team documents: Retrieve a paginated list of team documents.
  • Get document: Retrieve detailed information about a specific document by ID, including its status.
  • Revoke document: Cancel or stop an in-progress document.
  • Send reminders: Send reminders to signers who have not yet completed signing.
  • List templates: Retrieve a paginated list of templates available in the BoldSign account.
  • Get template: Retrieve detailed information about a specific template by ID.
  • Send document from template: Create and send a document for signing based on a preconfigured template.
  • List Contacts: Retrieve a paginated list of contacts in the BoldSign account.
  • Get Contact: Retrieve detailed information about a specific contact by ID.
  • List Users: Retrieve a paginated list of users in the BoldSign organization.
  • Get User: Retrieve detailed information about a specific user by ID.
  • List Teams: Retrieve a paginated list of teams in the BoldSign organization.
  • Get Team: Retrieve detailed information about a specific team by ID.

Usage

Prerequisites:

  • A BoldSign account: An account is required to obtain API credentials. You can sign up for a free trial, or use an existing sandbox or paid account.
  • BoldSign API credentials: Obtain the necessary application credentials, especially the API key. Instructions for generating and managing API keys are available in the BoldSign API documentation.
  • Node.js: Version 18.0.0 or later is required.
  • An MCP client: An MCP client application is required to interact with the server. Examples include Cursor, VS Code, Windsurf, Claude Desktop, Cline, or any other compatible MCP client.

Environment variables:

  • BOLDSIGN_API_KEY: The API key obtained from your BoldSign account.
  • BOLDSIGN_API_REGION: Specifies the region where your BoldSign account is located. Defaults to US when not specified. US means the United States region, EU means the Europe region, and CA means the Canada region.

Installation configuration in each client (official configuration snippets are provided and need to be added to the corresponding client settings or configuration files):

  • Cursor: It is recommended to add the configuration to the global Cursor MCP configuration file, usually located at ~/.cursor/mcp.json; you can also create .cursor/mcp.json in the project root directory for project-level installation.
  • Windsurf: Add the configuration snippet to the Windsurf MCP configuration file.
  • VS Code: Add the configuration to the VS Code settings file that manages the MCP server configuration.
  • Claude Desktop: Add the configuration to the Claude Desktop configuration file, usually named claude_desktop_config.json.
  • Cline: Add the configuration snippet to the Cline MCP configuration file.

Use cases

Suitable for scenarios where you need to operate BoldSign e-signature business through natural language or agent-based methods in MCP-supported LLM clients (such as Cursor, VS Code, Windsurf, Claude Desktop, Cline), including viewing and managing documents, templates, contacts, users, and teams, revoking in-progress documents, sending reminders to signers, and sending signature documents based on templates.

Limitations

  • This repository is deprecated, and the official recommendation is to use the hosted BoldSign MCP Server for improved authentication options, more features, and a fully managed experience.
  • A BoldSign account and API credentials are required.
  • Node.js 18.0.0 or later is required.
  • A compatible MCP client is required.
  • Specific configuration code snippets, pricing, and more limitation details are not yet fully provided in the materials.

License

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

Related tools

Browse category