Skip to content
BoldSign MCP

Send and track eSignature requests from your AI assistant

Ask Claude, ChatGPT, or GitHub Copilot to send a contract for signature. BoldSign does the sending, the chasing, and the record keeping.

Create your API sandboxBook a walkthrough
  • Works with your AI agent (Claude, ChatGPT, and Copilot)
  • No server to install or run
AI assistantConnected to BoldSign

Send the Mutual NDA to Emily Carter for signature.

I found your Mutual NDA template and Emily Carter, e•••@example.com. Should I send it to her now?

Yes, send it.

Sent to Emily Carter for signature.Document ID
8f2c4b1e-3d7a-4c9e-b5a1-2e6f0d9c7b34

Example conversation, sample data

Trusted by 50,000+ businesses worldwide

Samsonite
Ryanair
Hyatt
Sony
Crumbl Cookies
Payroc
Cost Plus
What it does

What can an AI assistant do with your eSignature account?

BoldSign MCP connects your AI assistant to your BoldSign account. It sends agreements from your templates and tells you who has signed.

  • Go from a chat to a signed agreement

    A chat starts, and the agreement goes out for signature from that same conversation. Your assistant reports its status when you ask.

    See it in a live demo

  • Send only your approved templates

    Your assistant fills in a template you approved and sends it. It never writes the agreement itself.

    See the controls

  • Chase signatures without a dashboard

    Ask who has not signed, then have your assistant send them a reminder.

    See every action

Controls

How much control do you keep when an AI agent sends a document?

You keep full control. BoldSign MCP sends only templates you approved, and the agent never writes or edits an agreement.

  • Your templates set the wording

    The agent can only send a template you built and approved in BoldSign beforehand.

  • Your access rules still apply

    The agent acts as the BoldSign account behind the API key or OAuth sign-in. It reaches nothing that account cannot reach.

  • Every send lands on the audit trail

    The audit trail records the sender's name, email, IP address, and device for each document.

  • The person still signs

    Your agent prepares and sends the request. The signature is made by the signer, on their own copy.

Why BoldSign

Why choose BoldSign for AI agent signing

BoldSign MCP adds eSignatures to the AI assistant your team already uses. There is no code to write and no server to run.

  • Works in the assistant you already use

    Claude, ChatGPT, and GitHub Copilot each have a BoldSign setup guide.

  • Ready in about 10 to 15 minutes

    You add the connector and sign in. The three steps are on this page.

  • No account needed to sign

    Signers open the request and sign on their own device, with no BoldSign login.

  • Test free before you pay

    The BoldSign API sandbox is free, so you can try each action first.

  • Help when you need it

    Reach the BoldSign team by chat, email, or support ticket. There is no support tier to buy.

Setup

How do you set up the connection in your AI client?

You add BoldSign to your AI client as a connector, sign in, and start asking. BoldSign runs the server, so you install nothing.

  1. Add BoldSign as a connector

    Paste the BoldSign MCP address into your AI client. The US, EU, Canada, and Australia each have their own address.

    Add custom connector
    NameBoldSign
    Server addresshttps://mcp.boldsign.com/mcp
    An AI client's add connector form with the name BoldSign and the BoldSign MCP address for the US region

  2. Sign in to BoldSign

    Claude and ChatGPT open a BoldSign sign-in page. Developer tools send an API key instead.

    Your AI assistant wants to access your BoldSign account

    It will be able to:

    • Send documents from your templates
    • Check status and send reminders
    • Read your contacts, users, and teams
    A BoldSign sign-in screen asking you to allow your AI assistant to send documents, check status and read contacts

  3. Ask for what you need

    From then on you write plain sentences. Your assistant takes the action in BoldSign and tells you what happened.

    AI assistantConnected to BoldSign

    Who has not signed the renewal yet?

    Sarah Mitchell is the only one left. Her copy was opened on Tuesday.

    Send her a reminder.

    Reminder sent to Sarah Mitchell. The document still shows as Sent in BoldSign.

    Example conversation, sample data

Works in: Claude, Claude Code, ChatGPT, and GitHub Copilot in Visual Studio Code. Other MCP clients work if they support remote connections.

Actions

Every eSignature action an AI agent can call

BoldSign MCP lets your AI agent take 14 actions in your BoldSign account. Your assistant picks the right one for each request.

Read how each action works

Documents

  • Send a contract

    BoldSign creates a signature request from your template and sends it.

  • See what is out

    BoldSign lists the documents in your account.

  • See the team’s documents

    BoldSign lists the documents your team access covers.

  • Check one document

    BoldSign returns its status and details.

  • Chase a signer

    BoldSign emails a reminder for a request still waiting.

  • Pull a contract back

    BoldSign cancels the document so nobody can sign it.

Templates

  • Find a template

    BoldSign lists the templates saved in your account.

  • Check a template

    BoldSign returns the details of one template.

Contacts

  • Look up who to send to

    BoldSign lists your saved contacts.

  • Get one contact

    BoldSign returns that contact’s details.

Users and teams

  • See your users

    BoldSign lists the users in your organization.

  • Get one user

    BoldSign returns that user’s details.

  • See your teams

    BoldSign lists the teams in your organization.

  • Get one team

    BoldSign returns that team’s details.

Live demo

Can you try an AI signing agent before you build one?

Yes. BoldSign runs working agent demos on a BoldSign demo account. You can watch a chat turn into a signed document before you connect anything of your own.

  • Chat with the agent

    You answer a few questions in the chat, the way your own customer would.

  • Watch the form arrive filled in

    The agent fills the template fields from the conversation, then sends the form for signature.

  • Pick the job closest to yours

    The demos cover warranty claims, HR onboarding, legal ops, and scholarship acceptance.

Try a live agent demo

Demo only. Documents signed in a demo are not legally binding, and no real case is processed.

Security

How are your documents and signer data kept secure?

BoldSign encrypts every document twice with AES-256. Its security controls are independently audited for SOC 2 Type 2. Each standard is listed in your account’s Compliance page, shown below.

Compliance

BoldSign meets global security and compliance standards to protect your documents and data. Manage the settings below to align with your organization’s requirements.

US flag

Data Residency

Active (US - Global)

Your documents and signer data are securely stored in your selected region to meet data sovereignty and local regulatory requirements.

View Data Residency Policy
HIPAA logo

HIPAA Compliance

Enabled

Enable HIPAA mode to protect PHI using administrative, technical, and physical safeguards aligned with HIPAA regulations.

View Details
PCI DSS logo

PCI DSS

Compliant

Payments are securely processed through Stripe, a PCI DSS Level 1-certified provider, ensuring the safe handling and encryption of all payment data.

View PCI DSS Policy
CCPA logo

CCPA & CPRA

Compliant

Ensures compliance with California privacy laws, giving residents transparency and control over their personal data, including rights to access, delete, and opt out.

View Privacy Policy
AICPA SOC logo

SOC 2 Type II

Compliant

BoldSign has successfully completed a SOC 2 Type II audit, validating our controls for security, availability, confidentiality, and data integrity.

Request SOC 2
US flag

UETA & ESIGN

Compliant

BoldSign ensures that all e-signatures are legally binding and compliant with the U.S. ESIGN Act and the Uniform Electronic Transactions Act (UETA).

View UETA & ESIGN Policy
EU flag

eIDAS (SES)

Compliant

BoldSign complies with the EU eIDAS Regulation (910/2014) and supports Simple Electronic Signatures (SES) by default.

View SES Policy
EU flag

eIDAS (QES)

Enabled

Enable Qualified Electronic Signatures (QES) for contracts requiring the highest legal assurance under eIDAS.

View QES Policy
The compliance panel in your BoldSign account.
Customer stories

Which teams build their signing workflow on BoldSign?

BoldSign customers who automate signing usually start with the eSignature API, and BoldSign MCP calls those same endpoints.

  • Payroc customer story Payroc

    A payments company put the BoldSign API inside its contract workflow

    Payroc brought contract sending into the system its team already works in.

    Watch or read the Payroc story
  • Lucile Brunin of Alliance Regulatory, customer story Alliance Regulatory

    A regulated document platform embeds signing and tracks status

    Lucile Brunin's team uses the BoldSign API for status tracking and signing with no account.

    Watch or read the Alliance Regulatory story
  • Martin Harrisson of Karborea, customer story Karborea

    Embedded signing cut the wait on contract turnaround

    Martin Harrisson's team uses BoldSign's embedded signing and follows each contract to signature.

    Watch or read the Karborea story
What it costs

Limits and costs to know before you connect an AI agent to BoldSign

BoldSign MCP sends signature requests and reports on them. It does not draft an agreement, and it does not sign for anyone. Prices are in USD.

  • $30 Enterprise API plan, a month, with 40 envelopes
  • $0.75 per envelope after that Live documents need that plan. Testing in the API sandbox is free.
See API plans and pricing
Good to know
  • 14 actions your agent can call The hosted server exposes no others.
  • 2,000 API requests an hour, per account The production limit, shared with your other API calls.
Related

More on building an AI agent that signs

  • Documentation

    BoldSign MCP server reference

    Endpoints, authentication, and the full tool list.

    Read the documentation
  • Guide

    Build your own agent with the API

    A worked tutorial that pairs the Claude API with BoldSign.

    Read the tutorial
  • Guide

    Connect BoldSign to Claude

    Add the connector, sign in, and send your first contract.

    Read the setup guide
Common questions

Questions about MCP and eSignatures

What is an eSignature MCP server?

An MCP server is a connector that exposes a product's actions as tools an AI agent can call. An eSignature MCP server exposes sending, tracking, and reminders. BoldSign hosts one for each of its regions.

Which AI assistants can connect to BoldSign MCP?

Claude Web, Claude Code, ChatGPT, and GitHub Copilot have their own setup guides. Any client that speaks the Model Context Protocol over a remote endpoint can be pointed at it too.

Do I need to write code to use BoldSign MCP?

No. In a chat client you add BoldSign as a connector and sign in, then write ordinary sentences. Code is only needed if you build your own integration on the BoldSign API.

Can an AI agent sign a document for me?

No. BoldSign MCP prepares and sends requests, and the named signer signs their own copy.

Are documents sent through an AI assistant legally binding?

Yes. Signatures you collect with BoldSign are legally binding under the ESIGN Act, UETA, and eIDAS. Sending through an AI assistant does not change how the signature is made.

How is BoldSign MCP different from the BoldSign API?

The API is the full developer interface, and your team codes against it. BoldSign MCP is a hosted layer over part of that API. It is shaped so an AI agent can call it without your code.

Get started

Let your assistant send the next contract

Connect BoldSign to your AI client and try every action before you pay.

Create your API sandboxBook a walkthrough
  • 30-day free trial
  • No credit card required

Last updated: October 18, 2026