BoldSign MCP

Created By
boldsigna year ago
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.
Overview

Overview

What is BoldSign MCP?

BoldSign MCP is a Model Context Protocol (MCP) server that enables Large Language Models (LLMs) to interact programmatically with the BoldSign API. It allows LLMs to manage documents, templates, contacts, users, and teams on BoldSign, acting as intelligent agents for e-signature workflows and document automation.

Key features of BoldSign MCP

  • Seamless integration with the BoldSign API for document and templates.
  • LLM-friendly, providing structured data and deterministic tool interfaces.
  • Supports a wide range of e-signature and document automation tasks.

Use cases of BoldSign MCP

  • Retrieve and automate document management.
  • Managing templates and sending documents from templates.
  • Retrieving and organizing contacts, users, and teams.
  • Building intelligent agents for e-signature workflows.

Server Config

{
  "mcpServers": {
    "boldsign": {
      "command": "npx",
      "args": [
        "-y",
        "@boldsign/mcp"
      ],
      "env": {
        "BOLDSIGN_API_KEY": "{YOUR_BOLDSIGN_API_KEY}",
        "BOLDSIGN_API_REGION": "US"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
boldsign
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago