Boldsign MCP Server

NodeJS client for boldsign

Local serverstdioTypeScript

What is the Boldsign MCP server?

If you already use Boldsign, the boldsign mcp server is the piece that lets your assistant work with it directly. NodeJS client for boldsign.

What the server does

Easily integrate BoldSign's e-signature features into your Node.js applications. This package simplifies sending documents for signature, embedding signing ceremonies, tracking document status, downloading signed documents, and managing e-signature workflows.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

Installation

Installation goes through your MCP client rather than a global install: point it at boldsign on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Credentials and setup notes

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Boldsign's toolset — Class, BrandingApi, ContactsApi and 9 more — is a fair guide to whether it matches your workflow. It is maintained by boldsign; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Boldsign.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
ClassMethod
BrandingApi[**brandList**](./docs/BrandingApi.md#brandlist)
ContactsApi[**contactUserList**](./docs/ContactsApi.md#contactuserlist)
CustomFieldApi[**createCustomField**](./docs/CustomFieldApi.md#createcustomfield)
DocumentApi[**addAuthentication**](./docs/DocumentApi.md#addauthentication)
GroupContactsApi[**createGroupContact**](./docs/GroupContactsApi.md#creategroupcontact)
IdentityVerificationApi[**createEmbeddedVerificationUrl**](./docs/IdentityVerificationApi.md#createembeddedverificationurl)
PlanApi[**apiCreditsCount**](./docs/PlanApi.md#apicreditscount)
SenderIdentitiesApi[**createSenderIdentities**](./docs/SenderIdentitiesApi.md#createsenderidentities)
TeamsApi[**createTeam**](./docs/TeamsApi.md#createteam)
TemplateApi[**addTag**](./docs/TemplateApi.md#addtag)
UserApi[**cancelInvitation**](./docs/UserApi.md#cancelinvitation)

How to install the Boldsign MCP server

{
  "mcpServers": {
    "boldsign": {
      "command": "npx",
      "args": ["-y", "boldsign"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

Example prompts to try

  • Use Boldsign to Class.
  • Use Boldsign to BrandingApi.
  • Use Boldsign to ContactsApi.

Frequently asked questions

It connects Boldsign to MCP-compatible AI assistants such as Claude and Cursor, exposing 12 tools (Class, BrandingApi, ContactsApi, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Boldsign directly.