MCP Server

1. An MCP-compatible client: VS Code (with GitHub Copilot), Cursor, Windsurf, Claude Desktop, Cline, or any client that supports MCP over HTTP.

No BoldSign API key is required, as the MCP server only accesses publicly available BoldSign documentation.

The BoldSign Assistant MCP server is available at:

https://developers-mcp.boldsign.com/mcp

This is a Streamable HTTP MCP server. It uses the Streamable HTTP transport and does not support stdio or SSE transports.

1. Copy the BoldSign Assistant MCP server URL: https://developers-mcp.boldsign.com/mcp
2. Add it to your MCP client configuration (see client-specific instructions below).
3. Restart or reload your client.
4. Open a new chat and ask:

"How do I send a document for signature using the BoldSign API?"

Option 1 - Command Palette (recommended):

1. Open the Command Palette (Ctrl+Shift+P)
2. Run MCP: Add Server
3. Select HTTP as the transport type
4. Enter https://developers-mcp.boldsign.com/mcp as the URL
5. Give it a name (e.g., BoldSign) and save

Option 2 - Manual config (~/.vscode/mcp.json or .vscode/mcp.json):

{
  "servers": {
    "BoldSign": {
      "type": "http",
      "url": "https://developers-mcp.boldsign.com/mcp"
    }
  }
}

Refer to the VS Code MCP documentation for more details.

Claude Web connects to the BoldSign Assistant MCP server as a remote connector:

1. Open Claude Web and go to Customize → Connectors in the sidebar
2. Click + to add a custom connector
3. Enter a name (e.g., BoldSign) and the server URL: https://developers-mcp.boldsign.com/mcp
4. Click Add, then Connect
5. Enable the connector in the conversation where you want to use it

Remote connector availability depends on your Claude plan.

Create or update a .mcp.json file in your project root:

{
  "mcpServers": {
    "BoldSign": {
      "type": "http",
      "url": "https://developers-mcp.boldsign.com/mcp"
    }
  }
}

After saving, start Claude Code in that project and run /mcp to confirm the boldsign server is connected and its tools are available.

Option 1 - Remote Servers UI:

1. In the Cline panel, click the MCP Servers icon
2. Open the Remote Servers tab
3. Enter server name BoldSign, paste https://developers-mcp.boldsign.com/mcp, select Streamable HTTP, and click Add Server

Option 2 - Manual config (cline_mcp_settings.json):

{
  "mcpServers": {
    "BoldSign": {
      "url": "https://developers-mcp.boldsign.com/mcp",
      "type": "streamableHttp"
    }
  }
}

Refer to the Cline MCP documentation for more details.

Once connected, you can ask the BoldSign Assistant MCP server questions directly in your AI client. Trigger phrases for best results:

• BoldSignAssistant
• /boldsign-assistant
• /boldsign
• @boldsign
• @ask_boldsign
• In VS Code: #BoldSignAssistant

Grant the server permission to run when prompted (per session, workspace, or always). Start a new chat for each new topic to keep context focused.

The BoldSign Assistant MCP server works across all supported AI interaction modes - Ask/Chat, Edit, and Agent - in compatible MCP clients.

• "#BoldSignAssistant How do I send a document for signature using the BoldSign API?"
• "@boldsign What are the required parameters for creating a template?"
• "/boldsign How do I set up a webhook to track when a document is signed?"
• "BoldSignAssistant Show me how to embed a signing experience in my web app."

Use a single prompt to generate a complete, working application wired up with BoldSign:

• ASP.NET Core: "Create an ASP.NET Core MVC app with a button to send a document for signing using the BoldSign .NET SDK."
• Node.js: "Build a Node.js Express app that sends a BoldSign document for signature when a form is submitted."
• Python: "Create a Python Flask app that uses the BoldSign SDK to send a document and track its status."
• Java: "Generate a Java Spring Boot application with a BoldSign integration to send and manage signature requests."