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
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago