Log inSubmit server
Boldsign MCP logo

Boldsign MCP

by boldsign

Connects MCP clients to BoldSign for managing documents, templates, contacts, users, and teams.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Boldsign MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "boldsign-boldsign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@boldsign/mcp"
      ],
      "env": {
        "BOLDSIGN_API_KEY": "YOUR_VALUE_HERE",
        "BOLDSIGN_API_REGION": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @boldsign/mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The boldsign/boldsign-mcp MCP server exposes selected BoldSign API operations for documents, templates, contacts, users, and teams. It runs locally through Node.js and communicates with MCP clients over stdio, using a BoldSign API key and regional setting. Reach for it when an agent needs to inspect signing activity, send documents from templates, or manage document workflows in BoldSign. The repository is deprecated, and its maintainers recommend the hosted BoldSign MCP Server for newer authentication options and features.

Use cases

  • List documents and check their signing status
  • Send reminders to pending signers
  • Create signing documents from templates
  • Inspect BoldSign contacts, users, and teams

Key features

  • List and inspect BoldSign documents
  • Revoke in-progress documents
  • Send signer reminders
  • Send documents from templates
  • Read contacts, users, and teams

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

18/18 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @boldsign/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads257Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Boldsign MCP works

What boldsign/boldsign-mcp does

The boldsign/boldsign-mcp MCP server lets an MCP-compatible application call selected BoldSign API operations through an agent interface. Its coverage is centered on e-signature administration: documents, templates, contacts, users, and teams.

For documents, it can retrieve paginated account or team listings, inspect a document's details and status, revoke an in-progress document, and send reminders to signers who have not completed their signatures. Template operations include listing templates, retrieving a template, and creating and sending a signing document from a configured template.

The server also exposes read operations for contacts, organization users, and teams. These operations retrieve lists or details by identifier rather than creating or modifying those records.

How it works

The project is a local MCP server launched with Node.js. An MCP client starts the server as a stdio process, and the server uses the supplied BoldSign credentials to call the BoldSign API.

The BoldSign account region is configurable. Supported values are US, EU, and CA; US is the default when no region is supplied. API responses and available operations depend on the connected BoldSign account and the API endpoints used by each tool.

Setup and configuration

Using the boldsign/boldsign-mcp MCP server requires a BoldSign account, an API key, Node.js 18 or later, and an MCP client. The local configuration uses the npm package @boldsign/mcp and runs it with npx.

Set these environment variables in the client configuration:

  • BOLDSIGN_API_KEY: The API key generated in the BoldSign account.
  • BOLDSIGN_API_REGION: The account region, using US, EU, or CA. If omitted, the server uses US.

For example, a stdio client configuration uses npx with -y @boldsign/mcp as its arguments. The exact configuration file depends on the client. Cursor uses an MCP JSON file, while Claude Desktop uses claude_desktop_config.json; the README provides equivalent examples for the other listed clients.

Tools and capabilities

Available capabilities are grouped by BoldSign resource:

  • Documents: list account documents, list team documents, get document details and status, revoke an in-progress document, and send signer reminders.
  • Templates: list templates, get template details, and send a document from a template.
  • Contacts: list contacts and retrieve contact details.
  • Users: list organization users and retrieve user details.
  • Teams: list organization teams and retrieve team details.

Document and template listing operations are paginated according to the corresponding BoldSign API endpoints.

Limitations and notes

The boldsign/boldsign-mcp MCP server repository is marked deprecated. The maintainers point users to the hosted BoldSign MCP Server for improved authentication options, additional features, and a fully managed deployment. This repository's setup therefore applies to the local npm-based server described in its README, not necessarily to the hosted replacement.

A BoldSign API credential is required, so this server is not credential-free. The listed tools also focus on the resources and actions documented above; no document upload, signing completion, webhook, or record-creation tool is described.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Boldsign MCP

Install Node.js 18 or later, then configure an MCP client to run `npx -y @boldsign/mcp` with the required BoldSign environment variables.

Set `BOLDSIGN_API_KEY`. `BOLDSIGN_API_REGION` is optional and accepts `US`, `EU`, or `CA`; it defaults to `US`.

Yes. The README includes Claude Desktop configuration using the local stdio command and the BoldSign environment variables.

It can manage listed document actions, work with templates, and retrieve contacts, users, and teams through the BoldSign API.

The repository is marked deprecated. Its maintainers recommend the hosted BoldSign MCP Server for improved authentication options, additional features, and managed operation.

Related MCP servers

All in Other Tools and Integrations All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBoldsign MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/boldsign-boldsign-mcp?style=directory)](https://allmcps.com/mcp/boldsign-boldsign-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/boldsign-boldsign-mcp"><img src="https://allmcps.com/api/badge/boldsign-boldsign-mcp?style=directory" alt="Boldsign MCP on AllMCPs" /></a>