Official description7 sourcesMCP servers8d ago
boldsign/boldsign-mcp
๐ โ๏ธ - Search, request and manage e-signature contracts with BoldSign
View on GitHub โDirect link ยท no redirect page
Config template (adjust for your client)
claude mcp add boldsign-mcp -- npx -y boldsign-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
- Star count
- 7 โ ยท boldsign/boldsign-mcp ยท read from the repository page ยท (checked 2026-10-16 20:00:20)
- Source
- collected from the punkpeye/awesome-mcp-servers list ยท type: MCP server
- Harvest history
- first seen 2026-10-09 ยท last seen 2026-10-16 ยท seen 32ร ยท listed by 7 sources
- Score
- score 703 ยท 7 โ ยท 7 sources ยท mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP ๆๅก. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
boldsign/boldsign-mcp๏ผfirst catalogued 2026-10-09๏ผlast seen 2026-10-16ใThere is no official certification or quality rating here โ we record sources and dates only.Third-party quality signals
BoldSign MCP Server
ไปฅไธๆๅฝ่ช่ฏฅไปๅบ็ README๏ผ็ๆฎต๏ผ ยท ๅจ GitHub ่ฏปๅฎๆด README โ
**Author:** Syncfusion
**Homepage:** https://boldsign.com
> [!WARNING]
> **This repository is deprecated.** For improved authentication options, additional features, and a fully managed experience, use the hosted BoldSign MCP Server instead.
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:
1. **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.
2. **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.
3. **Node.js:** Version 18.0.0 or higher is required.
4. **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 to US if not specified.
- US for the United States region.
- EU for the Europe region.
- CA for 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.
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:
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:
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:
**Homepage:** https://boldsign.com
> [!WARNING]
> **This repository is deprecated.** For improved authentication options, additional features, and a fully managed experience, use the hosted BoldSign MCP Server instead.
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:
1. **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.
2. **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.
3. **Node.js:** Version 18.0.0 or higher is required.
4. **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 to US if not specified.
- US for the United States region.
- EU for the Europe region.
- CA for 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.
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:
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:
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:
- Source
- awesome ยท https://github.com/boldsign/boldsign-mcp
- Browse by field
- MCP servers
- Traction
- 7 โ
- added
- yesterday
More in MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.