Overview

Let your AI agents send, track, and manage eSignature workflows by connecting to BoldSign's hosted MCP server that works with Claude, ChatGPT, coding editors, and autonomous agent pipelines.

The BoldSign MCP server exposes BoldSign's eSignature API as a set of tools that AI agents can call via the Model Context Protocol (MCP). Connect any compatible client to a hosted regional endpoint, authenticate, and your agent can immediately send documents from templates, monitor signing status, manage contacts, users, and teams through natural language.

BoldSign's hosted MCP server works with AI chat interfaces, coding editors, and autonomous agent pipelines. Select a client below for setup instructions:

• Claude - Add as a remote connector in Claude Web via OAuth, while Claude Code is a strong fit for API key-based .mcp.json setup
• ChatGPT - Add as a custom connector in ChatGPT Pro, Plus, Business, or Enterprise.
• GitHub Copilot - Visual Studio Code uses MCP configuration and API key authentication for the most direct setup path

If you use another MCP-compatible client that supports remote HTTP transport and custom headers, you can generally connect it with the BoldSign MCP endpoint and an X-API-Key header.

Choose the endpoint that matches the region of your BoldSign account. This is the canonical endpoint list for the BoldSign MCP Server documentation.

If you connect to the wrong region, authentication or downstream BoldSign requests can fail because the MCP endpoint, authorization system, and API region must align.

The hosted BoldSign MCP Server supports two authentication models on every regional endpoint.

Open Authentication for the full setup guidance, redirect URI details, and security considerations.

The hosted BoldSign MCP Server provides a focused set of tools for the most common account and signing workflows.

• list_documents - list documents in your account
• list_team_documents - list documents available through team-level access
• get_document_properties - retrieve document details, status, and related metadata
• send_reminder_for_document_sign - send reminder emails for pending signature requests
• revoke_document - cancel an in-progress document so it can no longer be signed

• list_templates - browse templates in your BoldSign account
• get_template_properties - retrieve the details of a specific template
• send_document_from_template - create and send a signature request from an existing template

• list_contacts - list saved contacts
• get_contact - retrieve a specific contact's details

• list_users - list users in your organization
• get_user - retrieve details for a specific user

• list_teams - list teams in your organization
• get_team - retrieve details for a specific team

For server-to-server workflows that run without a human in the loop, pass your BoldSign API key as the X-API-Key header in every request. The hosted MCP server is stateless and does not distinguish between interactive and automated callers.

Example read-first prompts:

• List all templates and show which ones were used most recently.
• Which documents sent this week still have pending signers?
• Who are the members of the Legal team in my BoldSign organization?

Example action-oriented prompts:

• Send the NDA template to Sarah Nguyen at [email protected] and set expiry to 30 days.
• Send reminders to all signers who have not completed the vendor agreement.

Before you connect a client, keep these points in mind:

• The MCP endpoint must match your BoldSign account region.
• Use the dedicated client guides so the region, authentication flow, and setup steps stay aligned to that client.
• Requests that originate from a browser are rejected. This protects against exposing API keys or OAuth tokens in browser contexts.
• For a first validation, prefer read-only prompts before relying on mutating tools.

• Review Authentication to choose between API key and OAuth