---
title: "BoldSign MCP: eSignature MCP Server for Your AI Assistant"
description: "Connect Claude, ChatGPT, or Copilot to BoldSign MCP. Send contracts from approved templates, see who has signed, and send reminders from your AI assistant."
url: "https://boldsign.com/mcp-ai-esignature-assistant/"
---

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 sandbox](https://account.boldsign.com/signup?planId=1076)[Book a walkthrough](https://boldsign.com/request-demo.md)

- Works with your AI agent (Claude, ChatGPT, and Copilot)
- No server to install or run

*Picture: Example chat: you ask the AI assistant to send the Mutual NDA to Daniel Ortiz; it sends the document from the template with BoldSign, and Daniel will get a BoldSign email with a link to sign*

Trusted by 100,000+ organizations worldwide

*Picture: BoldSign rated 4.7 out of 5 on G2*

![Samsonite](https://boldsign.com/assets/landing/trustbar/samsonite.svg)

![Ryanair](https://boldsign.com/assets/landing/trustbar/ryanair.svg)

![Hyatt](https://boldsign.com/assets/landing/trustbar/hyatt.svg)

![Sony](https://boldsign.com/assets/landing/trustbar/sony.svg)

![Crumbl Cookies](https://boldsign.com/assets/landing/trustbar/crumbl.svg)

![Payroc](https://boldsign.com/assets/landing/trustbar/payroc.svg)

![Cost Plus](https://boldsign.com/assets/landing/trustbar/costplus.svg)

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](#bs-mcp-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](#bs-mcp-control)

- ### Chase signatures without a dashboard

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

  [See every action](#bs-mcp-tools)

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](https://support.boldsign.com/kb/article/14647) 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](https://developers.boldsign.com/boldsign-mcp-server/claude-web/).

- ### Ready in about 10 to 15 minutes

  You add the connector and sign in. [The three steps](#bs-mcp-setup) 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](https://account.boldsign.com/signup?planId=1076) is free, so you can try each action first.

- ### Help when you need it

  Reach the BoldSign team by chat, email, or [support ticket](https://support.boldsign.com/). 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](https://developers.boldsign.com/boldsign-mcp-server/overview/).

   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](https://developers.boldsign.com/boldsign-mcp-server/authentication/) 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](https://developers.boldsign.com/boldsign-mcp-server/overview/)

### 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](https://boldsign.com/ai-esignature.md)

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.

Settings

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](https://boldsign.com/assets/landing/compliance/residency-de93bd.svg) 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](https://boldsign.com/security-policy.md)

- ![HIPAA logo](https://boldsign.com/assets/landing/compliance/hipaa-c34e9b.png) HIPAA Compliance

  Enabled

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

  [View Details](https://boldsign.com/hipaa-overview.md)

- ![PCI DSS logo](https://boldsign.com/assets/landing/compliance/pci-960f14.png) 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](https://boldsign.com/security-policy.md)

- ![CCPA logo](https://boldsign.com/assets/landing/compliance/ccpa-e62333.png) 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](https://boldsign.com/privacy-policy.md)

- ![AICPA SOC logo](https://boldsign.com/assets/landing/compliance/soc2-b31494.png) 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](https://boldsign.com/soc2-overview.md)

- ![US flag](https://boldsign.com/assets/landing/compliance/esign-de93bd.svg) 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](https://boldsign.com/ueta-and-esign-act-compliance.md)

- ![EU flag](https://boldsign.com/assets/landing/compliance/eidas-ses-677fe1.svg) eIDAS (SES)

  Compliant

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

  [View SES Policy](https://boldsign.com/simple-electronic-signature-compliance.md)

- ![EU flag](https://boldsign.com/assets/landing/compliance/eidas-qes-677fe1.svg) eIDAS (QES)

  Enabled

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

  [View QES Policy](https://boldsign.com/qes-overview.md)

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](https://boldsign.com/images/shared/payroc-img.svg) 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](https://boldsign.com/customer-stories/payroc.md)

- ![Lucile Brunin of Alliance Regulatory, customer story](https://boldsign.com/images/shared/lucile-brunin-customer.webp) 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](https://boldsign.com/customer-stories/lucile-brunin.md)

- ![Martin Harrisson of Karborea, customer story](https://boldsign.com/images/shared/martin-harrisson.webp) 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](https://boldsign.com/customer-stories/martin-harrisson.md)

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](https://boldsign.com/electronic-signature-pricing/?plan=api)

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](https://developers.boldsign.com/boldsign-mcp-server/overview/)

- Guide

  ### Build your own agent with the API

  A worked tutorial that pairs the Claude API with BoldSign.

  [Read the tutorial](https://boldsign.com/blogs/build-ai-agent-boldsign-mcp-claude-api.md)

- Guide

  ### Connect BoldSign to Claude

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

  [Read the setup guide](https://developers.boldsign.com/boldsign-mcp-server/claude-web/)

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](https://developers.boldsign.com/boldsign-mcp-server/overview/) 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](https://developers.boldsign.com/boldsign-mcp-server/chatgpt/). 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](https://boldsign.com/esignature-api.md).

### Can an AI agent sign a document for me?

No. BoldSign MCP prepares and sends requests, and the named signer [signs their own copy](https://support.boldsign.com/kb/article/575).

### 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](https://boldsign.com/electronic-signature-legality.md). Sending through an AI assistant does not change how the signature is made.

### How is BoldSign MCP different from the BoldSign API?

The [API](https://boldsign.com/esignature-api.md) 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 sandbox](https://account.boldsign.com/signup?planId=1076)[Book a walkthrough](https://boldsign.com/request-demo.md)

- 30-day free trial
- No credit card required

*Picture: A completed employment contract: signed by John Doe on 11/03/2026, all parties have signed*

Last updated: October 18, 2026
