Search
DemosSupport
Region
Create API Sandbox
Go To Home/Getting Started/BoldSign Assistant
  • BoldSign AI Assistant
    Chat with the BoldSign AI Assistant
  • Copy page
    Copy original Markdown file
  • View as Markdown
    Open plain Markdown file
  • Open in ChatGPT
    Ask ChatGPT about this page
  • Open in Claude
    Ask Claude about this page
  • Connect with MCP
    Add this MCP to any compatible client
  • Connect to Claude Code
    Use this MCP in Claude Code
  • Connect to Codex
    Use this MCP in Codex
Go To Home>Getting Started>BoldSign Assistant
  • BoldSign AI Assistant
    Chat with the BoldSign AI Assistant
  • Copy page
    Copy original Markdown file
  • View as Markdown
    Open plain Markdown file
  • Open in ChatGPT
    Ask ChatGPT about this page
  • Open in Claude
    Ask Claude about this page
  • Connect with MCP
    Add this MCP to any compatible client
  • Connect to VSCode
    Use this MCP in VS Code
  • Connect to Claude Code
    Use this MCP in Claude Code
  • Connect to Codex
    Use this MCP in Codex

Overview

The BoldSign AI Coding Assistant helps you integrate BoldSign APIs and SDKs faster. Powered by the BoldSign Assistant MCP server, a queryable layer over the BoldSign developer documentation. It gives your AI assistant real-time access to accurate API references, code guidance, and integration patterns without leaving your development environment.

Note: The BoldSign Assistant MCP server does not perform any eSignature actions such as sending documents, initiating signing workflows, or making live API calls.

The BoldSign Assistant MCP server is available as a streamable HTTP MCP server at:

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

No API key or additional dependencies are required to connect. Simply add this URL to your MCP-compatible client and start asking questions.

  • Search and retrieve content from BoldSign developer documentation

  • Answer questions about BoldSign API endpoints, parameters, and workflows

  • Provide code guidance for sending documents, managing templates, setting up webhooks, and more

  • Help troubleshoot integration issues with documentation-backed context

  • Scaffold complete, working applications from a single prompt across supported SDKs and frameworks. For example:

    "Create a ASP.NET Core MVC application with an option to send the document for signing using BoldSign API"

  1. Connect: Add https://developers-mcp.boldsign.com/mcp to your MCP-compatible client (VS Code, Cursor, Claude Desktop, Windsurf, or Cline).
  2. Query: Ask the assistant about BoldSign APIs, SDKs, webhooks, templates, embedded signing, and more.
  3. Build: Apply the code snippets and guidance to integrate BoldSign into your project.

For detailed setup instructions for each client, see the MCP Server page.

  • Validate generated code: Review and test AI-generated snippets before deploying to production.
  • Use sandbox accounts: Test integrations with a BoldSign sandbox account before going live.
  • Start fresh for new topics: Open a new chat when switching workflows to keep context focused.
  • Use advanced models: For best results, use GPT-4o, GPT-5, or Claude Sonnet 4.5+.
  • The MCP server only reads publicly published BoldSign documentation - it does not access your files, workspace, or account data.
  • Prompts are not stored, reused, or used to train BoldSign models.
  • Documentation context is retrieved by the MCP server; all output is generated by your selected AI model.