BoldSign MCP Server
Bridge Large Language Models with BoldSign's e-signature API via the Model Context Protocol.
Key Features
Use Cases
README
BoldSign MCP Server
Author: Syncfusion
Homepage: https://boldsign.com
An MCP server designed to facilitate interaction between Large Language Models (LLMs) and the BoldSign API. The Model Context Protocol (MCP) extends LLM capabilities, enabling them to act as agents when connecting with external systems.
This project contains various tools that interact with the BoldSign API to manage templates and documents for your e-signature.
Prerequisites
Before you begin, ensure you have the following installed and set up:
- 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.
- 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.
- Node.js: Version 18.0.0 or higher is required.
- 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 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 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 toUSif not specified.-
USfor the United States region. -
EUfor the Europe region. -
CAfor the Canada region.
-
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": {
"command": "npx",
"args": ["-y", "@boldsign/mcp"],
"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": {
"command": "npx",
"args": ["-y", "@boldsign/mcp"],
"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": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@boldsign/mcp"],
"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": {
"command": "npx",
"args": ["-y", "@boldsign/mcp"],
"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": {
"command": "npx",
"args": ["-y", "@boldsign/mcp"],
"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.
Available Tools
This MCP server provides access to the following tools via the BoldSign API:
Documents
-
List documents: Retrieves a paginated list of your documents.
-
List team documents: Retrieves a paginated list of team documents.
-
Get document: Retrieves detailed information, including status, for a specific document using its ID.
-
Revoke document: Allows you to cancel or call off a document that is in progress.
-
Send reminders: Sends reminders to signers who have not yet completed their signature on a document.
Templates
-
List templates: Retrieves a paginated list of templates available in your BoldSign account.
-
Get template: Retrieves detailed information for a specific template using its ID.
-
Send document from template: Creates and sends out a document for signing based on a pre-configured template.
Contacts
-
List Contacts: Retrieves a paginated list of contacts from your BoldSign account.
-
Get Contact: Retrieves detailed information for a specific contact using their ID.
Users
-
List Users: Retrieves a paginated list of users in your BoldSign organization.
-
Get User: Retrieves detailed information for a specific user using their ID.
Teams
-
List Teams: Retrieves a paginated list of teams in your BoldSign organization.
-
Get Team: Retrieves detailed information for a specific team using their ID.
Repository
https://github.com/boldsign/boldsign-mcp
Bug Tracker
https://github.com/boldsign/boldsign-mcp/issues
License
This project is licensed under the MIT License. See the LICENSE file for details.
Star History
Repository Owner
Organization
Repository Details
Programming Languages
Tags
Topics
Join Our Newsletter
Stay updated with the latest AI tools, news, and offers by subscribing to our weekly newsletter.
Related MCPs
Discover similar Model Context Protocol servers
mcp-server-esignatures
MCP eSignature server for drafting, managing, and sending digital contracts.
mcp-server-esignatures acts as a Model Context Protocol (MCP) server tailored for eSignature workflows. It provides a suite of tools to create, manage, and send digital contracts and templates through a standardized interface. The server supports actions like drafting contracts, managing templates, inviting collaborators, and integrating securely with the eSignatures.com API. Authentication and environment configuration streamline setup for both development and production environments.
- ⭐ 30
- MCP
- esignaturescom/mcp-server-esignatures
Plane MCP Server
Enables LLMs to manage Plane.so projects and issues via the Model Context Protocol.
Plane MCP Server provides a standardized interface to connect large language models with Plane.so project management APIs. It enables LLMs to interact directly with project and issue data, supporting tasks such as listing projects, retrieving detailed information, creating and updating issues, while prioritizing user control and security. Installation is streamlined through tools like Smithery, and configuration supports multiple clients including Claude for Desktop.
- ⭐ 32
- MCP
- kelvin6365/plane-mcp-server
Notion MCP Server
Enable LLMs to interact with Notion using the Model Context Protocol.
Notion MCP Server allows large language models to interface with Notion workspaces through a Model Context Protocol server, supporting both data retrieval and editing capabilities. It includes experimental Markdown conversion to optimize token usage for more efficient communication with LLMs. The server can be configured with environment variables and controlled for specific tool access. Integration with applications like Claude Desktop is supported for seamless automation.
- ⭐ 834
- MCP
- suekou/mcp-notion-server
MyMCP Server (All-in-One Model Context Protocol)
Powerful and extensible Model Context Protocol server with developer and productivity integrations.
MyMCP Server is a robust Model Context Protocol (MCP) server implementation that integrates with services like GitLab, Jira, Confluence, YouTube, Google Workspace, and more. It provides AI-powered search, contextual tool execution, and workflow automation for development and productivity tasks. The system supports extensive configuration and enables selective activation of grouped toolsets for various environments. Installation and deployment are streamlined, with both automated and manual setup options available.
- ⭐ 93
- MCP
- nguyenvanduocit/all-in-one-model-context-protocol
Raindrop.io MCP Server
Enable LLMs to manage and search Raindrop.io bookmarks via the Model Context Protocol.
Raindrop.io MCP Server is an integration that allows large language models to interact with Raindrop.io bookmarks using the Model Context Protocol. It provides tools to create and search bookmarks, including filtering by tags, and is designed for interoperability with environments like Claude for Desktop. Installation can be done via Smithery or manually, and configuration is managed through environment variables. The project is open source and optimized for secure, tokenized access to Raindrop.io.
- ⭐ 63
- MCP
- hiromitsusasaki/raindrop-io-mcp-server
Model Context Protocol Server for Home Assistant
Seamlessly connect Home Assistant to LLMs for natural language smart home control via MCP.
Enables integration between a local Home Assistant instance and language models using the Model Context Protocol (MCP). Facilitates natural language monitoring and control of smart home devices, with robust API support for state management, automation, real-time updates, and system administration. Features secure, token-based access, and supports mobile and HTTP clients. Designed to bridge Home Assistant environments with modern AI-driven automation.
- ⭐ 468
- MCP
- tevonsb/homeassistant-mcp
Didn't find tool you were looking for?