---
title: "BoldSign MCP server for AI agents - actionlake"
description: "Give Claude 80 BoldSign actions through one MCP server: documents, templates, users. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/boldsign
updated: 2026-10-23
---

Connectors · Files & documents

# BoldSign MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to BoldSign and the rest of your systems. It gives your agent 80 BoldSign actions (22 reads, 49 writes and 9 that wait for a confirmation) and holds the BoldSign credential itself, so the agent never does. It paces BoldSign's limits and records every call.

[Connect BoldSign free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "boldsign.contacts.list",
  intent: "check which BoldSign account is connected"
}
# List Contact document. · read · 1 upstream call
```

- 80 actions in one signed file
- 22 read look, never change
- 49 write create and update
- 9 wait for a yes destructive, confirmed first

Set up

## Connect BoldSign in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect BoldSign.
   API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `api_key` BoldSign API key: in the BoldSign web app open API > API Key and generate a key (sandbox or live)
   - `host` Where your BoldSign lives: your host
   ```
   account { op: "connections.requirements", service: "boldsign" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "boldsign.contacts.list" }
   # list contact document. · read · 1 upstream call
   check { action: "boldsign.contacts.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

BoldSign at a glance

**Sign-in**

API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.

**You provide**

`api_key`

**Setup fields**

`host`

**Limits we pace to**

2,000 calls an hour, per connection

**API covered**

BoldSign API v1 (OpenAPI 3.0.4)`api.boldsign.com`

**Built from**

BoldSign's documentation, read 23 October 2026[api.boldsign.com](https://api.boldsign.com/swagger/v1/swagger.json) [developers.boldsign.com](https://developers.boldsign.com/api-overview/getting-started/)

**Service file**

Version 1.0.0, signed (Ed25519)

**Cached reads**

20 of 22 reads, for up to 5 minutes; a write clears what it affects

**Shared entities**

2, so ask can line BoldSign up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in BoldSign.

80 actions in 11 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **22** read look, never change
- **49** write create and update
- **9** destructive wait for a confirmation

1. ### Documents
   23
   5 read · 16 write · 2 destructive
   List user documents. · Sends the document for sign. · Sends a draft-status document out for signature. · Get summary of the document.
2. ### Templates
   16
   2 read · 13 write · 1 destructive
   List all the templates. · Creates a new template. · Get summary of the template. · Edit and updates an existing template.
3. ### Users
   8
   2 read · 5 write · 1 destructive
   List user documents. · Get summary of the user. · Update new User role. · Create the user.
4. ### Sender identities
   7
   2 read · 4 write · 1 destructive
   Creates sender identity. · Lists sender identity. · Gets sender identity by ID or email. · Rerequests denied sender identity.
5. ### Contact groups
   5
   2 read · 2 write · 1 destructive
   List Group Contacts. · Create a new Group Contact. · Get Summary of the Group Contact. · Update the Group Contact.
6. ### Contacts
   5
   2 read · 2 write · 1 destructive
   List Contact document. · Create the new Contact. · Get summary of the contact. · Update the contact.
7. ### Custom fields
   5
   1 read · 3 write · 1 destructive
   Create the custom field. · Generates a URL for creating or modifying custom fields within your application's embedded · List the custom fields respective to the brand id. · Edit the custom field.
8. ### Brands
   4
   2 read · 1 write · 1 destructive
   List all the brands. · Get the specific brand details. · Reset default brand. · Delete the brand.

**3 more areas · 7 actions**

- Teams **4**
- Identity verification **2**
- Plan **1**

Top actions

## The BoldSign API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 24 of BoldSign's 25 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `boldsign.contacts.list` List Contact document. | List Contact document. | read | `crm.contact.list` 177 connectors |
| `boldsign.users.list` List user documents. | List user documents. | read | `identity.user.list` 474 connectors |
| `boldsign.contacts.create` Create the new Contact. | Create the new Contact. | write | `crm.contact.create` 161 connectors |
| `boldsign.users.get` Get summary of the user. | Get summary of the user. | read | `identity.user.get` 399 connectors |
| `boldsign.contacts.delete` Deletes a contact. | Deletes a contact. | destructive | `crm.contact.delete` 147 connectors |
| `boldsign.documents.list` List user documents. | List user documents. | read | `content.signature_request.list` 10 connectors |
| `boldsign.documents.send` Sends the document for sign. | Sends the document for sign. | write | `content.signature_request.create` 9 connectors |
| `boldsign.templates.list` List all the templates. | List all the templates. | read | `content.signature_template.list` 7 connectors |
| `boldsign.templates.create` Creates a new template. | Creates a new template. | write | `content.signature_template.create` 5 connectors |
| `boldsign.contact_groups.list` List Group Contacts. | List Group Contacts. | read | `crm.contact_list.list` 34 connectors |
| `boldsign.contact_groups.create` Create a new Group Contact. | Create a new Group Contact. | write | `crm.contact_list.create` 29 connectors |
| `boldsign.teams.create` Create Team. | Create Team. | write | this connector |

Try it

## Prompts to paste into Claude.

Each one names the BoldSign actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Find the BoldSign contacts with no email address, so we can clean them up.
   calls `boldsign.contacts.list`
2. Write write
   Create the new Contact in BoldSign. Show me exactly what you will send before you save it.
   calls `boldsign.contacts.create`
3. Across systems read
   Which contacts are in both BoldSign and HaloPSA, and how many are in only one of them?
   calls `boldsign.contacts.list` `halopsa.users.list`

Across your systems

## BoldSign, joined to the rest of your business.

One `ask` fetches from BoldSign and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

- Which contacts are in both BoldSign and HaloPSA, and how many are in only one of them?
  `boldsign.contacts.list` + `halopsa.users.list`, on `crm.contact` · [HaloPSA](https://actionlake.com/connectors/halopsa)
- Which contacts are in both BoldSign and NetSuite, and how many are in only one of them?
  `boldsign.contacts.list` + `netsuite.views.contacts`, on `crm.contact` · [NetSuite](https://actionlake.com/connectors/netsuite)

Also mapped by other connectors `identity.user` **517** `crm.contact` **192**

ask

```
ask {
  intent: "which contacts are in both BoldSign and HaloPSA, and how many are in only one of them",
  steps: [
    { action: "boldsign.contacts.list", as: "people", input: {}, limit: 100, max_pages: 5 },
    { action: "halopsa.users.list", as: "people2", input: {}, limit: 100, max_pages: 5 },
    { join: {
        left: "people",
        right: "people2",
        on: "crm.contact",
        group_by: "people.email",
        select: ["people.email", "count(people2.id) as in_halopsa"]
    } }
  ]
}
```

Example. Run it through check first: it validates the steps and prices them, and it is free.

Governance for BoldSign

## Destructive actions wait for a yes.

9 BoldSign actions are destructive. These are all of them:

- Deletes a contact. `boldsign.contacts.delete`
- Delete the document. `boldsign.documents.delete`
- Deletes a template. `boldsign.templates.delete`
- Revoke the document. `boldsign.documents.revoke`
- Deletes a Group Contact. `boldsign.contact_groups.delete`
- Cancel the users invitation. `boldsign.users.cancel_invitation`
- Delete the brand. `boldsign.brands.delete`
- Delete the custom field. `boldsign.custom_fields.delete`
- Deletes sender identity. `boldsign.sender_identities.delete`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do boldsign.contacts.delete confirm_policy: **human**

Deletes a contact.?

**intent:** the user asked me to deletes a contact.

run suspended · waiting for a named person · key _boldsign-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "boldsign-agent",
  allowed_actions: ["boldsign.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "boldsign.contacts.delete", approver: "lead@example.com" },
    { match: "boldsign.documents.delete", approver: "lead@example.com" },
    { match: "boldsign.templates.delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to BoldSign only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What BoldSign costs on actionlake.

Every BoldSign action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call BoldSign refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 80 BoldSign actions
- 80 actions page each page of a long list is one call
- 20 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every BoldSign action.

80 actions by area: the id your agent calls, what it does, and its effect.

**Documents 23**

- `boldsign.documents.add_authentication` The add authentication to recipient. write
- `boldsign.documents.add_tags` Add the Tags in Documents. write
- `boldsign.documents.cancel_editing` Cancels editing for a document that is currently in edit-mode. write
- `boldsign.documents.change_access_code` Changes the access code for the given document signer. write
- `boldsign.documents.change_recipient` Change recipient details of a document. write
- `boldsign.documents.create_embedded_clone_url` Generates a URL to embeds Clone document process into your application. write
- `boldsign.documents.create_embedded_edit_url` Generates an embedded edit URL that allows the document editing process to be integrated i write
- `boldsign.documents.create_embedded_request_url` Generates a send URL which embeds document sending process into your application. write
- `boldsign.documents.delete` Delete the document. destructive
- `boldsign.documents.delete_tags` Delete the Tags in Documents. write
- `boldsign.documents.extend_expiry` Extends the expiration date of the document. write
- `boldsign.documents.get` Get summary of the document. read
- `boldsign.documents.get_embedded_sign_link` Get sign link for Embedded Sign. read
- `boldsign.documents.list` List user documents. read
- `boldsign.documents.list_behalf` Gets the behalf documents. read
- `boldsign.documents.list_team` Get user Team documents. read
- `boldsign.documents.prefill_fields` Updates the value (prefill) of the fields in the document. write
- `boldsign.documents.remind` Send reminder to pending signers. write
- `boldsign.documents.remove_authentication` Remove the access code for the given document signer. write
- `boldsign.documents.revoke` Revoke the document. destructive
- `boldsign.documents.send` Sends the document for sign. write
- `boldsign.documents.send_draft` Sends a draft-status document out for signature. write
- `boldsign.documents.update` Edit and updates an existing document. write

**Templates 16**

- `boldsign.templates.add_tags` Add the Tags in Templates. write
- `boldsign.templates.create` Creates a new template. write
- `boldsign.templates.create_embedded_clone_url` Generates a URL to embeds Clone template process into your application. write
- `boldsign.templates.create_embedded_edit_url` Generates an edit URL to embeds template edit process into your application. write
- `boldsign.templates.create_embedded_preview_url` Generates a preview URL for a template to view it. write
- `boldsign.templates.create_embedded_request_url` Generates a send URL using a template which embeds document sending process into your appl write
- `boldsign.templates.create_embedded_template_url` Generates a create URL to embeds template create process into your application. write
- `boldsign.templates.delete` Deletes a template. destructive
- `boldsign.templates.delete_tags` Delete the Tags in Templates. write
- `boldsign.templates.get` Get summary of the template. read
- `boldsign.templates.list` List all the templates. read
- `boldsign.templates.merge_and_send` Send the document by merging multiple templates. write
- `boldsign.templates.merge_create_embedded_request_url` Generates a merge request URL using a template that combines document merging and sending write
- `boldsign.templates.send` Send a document for signature using a Template. write
- `boldsign.templates.share` Share a template with teams and manage permissions. write
- `boldsign.templates.update` Edit and updates an existing template. write

**Users 8**

- `boldsign.users.cancel_invitation` Cancel the users invitation. destructive
- `boldsign.users.change_team` Change users to other team. write
- `boldsign.users.create` Create the user. write
- `boldsign.users.get` Get summary of the user. read
- `boldsign.users.list` List user documents. read
- `boldsign.users.resend_invitation` Resend the users invitation. write
- `boldsign.users.update` Update new User role. write
- `boldsign.users.update_metadata` Update new User meta data details. write

**Sender identities 7**

- `boldsign.sender_identities.create` Creates sender identity. write
- `boldsign.sender_identities.delete` Deletes sender identity. destructive
- `boldsign.sender_identities.get` Gets sender identity by ID or email. read
- `boldsign.sender_identities.list` Lists sender identity. read
- `boldsign.sender_identities.rerequest` Rerequests denied sender identity. write
- `boldsign.sender_identities.resend_invitation` Resends sender identity invitation. write
- `boldsign.sender_identities.update` Updates sender identity. write

**Contact groups 5**

- `boldsign.contact_groups.create` Create a new Group Contact. write
- `boldsign.contact_groups.delete` Deletes a Group Contact. destructive
- `boldsign.contact_groups.get` Get Summary of the Group Contact. read
- `boldsign.contact_groups.list` List Group Contacts. read
- `boldsign.contact_groups.update` Update the Group Contact. write

**Contacts 5**

- `boldsign.contacts.create` Create the new Contact. write
- `boldsign.contacts.delete` Deletes a contact. destructive
- `boldsign.contacts.get` Get summary of the contact. read
- `boldsign.contacts.list` List Contact document. read
- `boldsign.contacts.update` Update the contact. write

**Custom fields 5**

- `boldsign.custom_fields.create` Create the custom field. write
- `boldsign.custom_fields.create_embedded_url` Generates a URL for creating or modifying custom fields within your application's embedded write
- `boldsign.custom_fields.delete` Delete the custom field. destructive
- `boldsign.custom_fields.list` List the custom fields respective to the brand id. read
- `boldsign.custom_fields.update` Edit the custom field. write

**Brands 4**

- `boldsign.brands.delete` Delete the brand. destructive
- `boldsign.brands.get` Get the specific brand details. read
- `boldsign.brands.list` List all the brands. read
- `boldsign.brands.reset_default` Reset default brand. write

**Teams 4**

- `boldsign.teams.create` Create Team. write
- `boldsign.teams.get` Get Team details. read
- `boldsign.teams.list` List Teams. read
- `boldsign.teams.update` Update Team. write

**Identity verification 2**

- `boldsign.identity_verification.create_embedded_url` Generate a URL that embeds manual ID verification for the specified document signer into y write
- `boldsign.identity_verification.get_report` Retrieve the ID verification report for the specified document signer. read

**Plan 1**

- `boldsign.plan.get_api_credits` Gets the Api credits details. read

Questions

## The BoldSign MCP server, answered.

**Is there a BoldSign MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 80 BoldSign actions across documents, templates, users and sender identities, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by BoldSign.

**What do I need to connect BoldSign?**

BoldSign API key: in the BoldSign web app open API > API Key and generate a key (sandbox or live). Plus your host. The free call account { op: "connections.requirements", service: "boldsign" } lists exactly what to paste.

**Can an AI agent delete or change things in BoldSign?**

Only if its key allows it, and only with an explicit confirmation. 9 BoldSign actions are destructive, including deletes a contact., delete the document. and deletes a template.. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my BoldSign API limit?**

actionlake paces every call to the limits in the BoldSign service file: 2,000 calls an hour per connection. Repeated reads are answered from cache (20 BoldSign actions can be), which never reaches BoldSign.

**What does a BoldSign action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (80 BoldSign actions page). Cache hits, searches, dry runs and calls BoldSign refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which BoldSign API does it cover?**

The BoldSign API v1 (OpenAPI 3.0.4) at api.boldsign.com by default, or the base URL set when you connect. It is built from BoldSign's documentation as read on 23 October 2026. 80 actions in 11 areas, each one in the signed service file (version 1.0.0).

**Can I combine BoldSign with my other systems?**

Yes. ask joins BoldSign to HaloPSA or NetSuite on the same customer and returns the answer rather than every row. BoldSign maps crm.contact, which 192 other connectors also map.

**Does actionlake keep my BoldSign data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your BoldSign credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like BoldSign

Shares the most action names with

- [DocuSign 22](https://actionlake.com/connectors/docusign)
- [PandaDoc 18](https://actionlake.com/connectors/pandadoc)
- [Adobe Acrobat Sign 11](https://actionlake.com/connectors/adobe-acrobat-sign)
- [signNow 10](https://actionlake.com/connectors/signnow)
- [Dropbox Sign 8](https://actionlake.com/connectors/dropbox-sign)
- [Concord 5](https://actionlake.com/connectors/concord)

Joins with, on shared entities

- [HaloPSA 2](https://actionlake.com/connectors/halopsa)
- [Microsoft 365 Users 2](https://actionlake.com/connectors/microsoft-365-users)
- [Salesforce Sales Cloud 2](https://actionlake.com/connectors/salesforce-sales-cloud)
- [Genesys Cloud CX 2](https://actionlake.com/connectors/genesys-cloud-cx)
- [Bitrix24 2](https://actionlake.com/connectors/bitrix24)
- [NetBox 2](https://actionlake.com/connectors/netbox)

Browse

- [All Files & documents connectors](https://actionlake.com/connectors/category/files-and-documents)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by BoldSign; the name is the vendor's own. Counts are from the BoldSign service file, version 1.0.0.

## Give your agent BoldSign today.

[Connect BoldSign free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/boldsign
More: https://actionlake.com/llms.txt
