X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Boldsign to Claude

Connect Claude Web, Desktop and Cowork to Boldsign MCP. Send a contract to client for signature, list all documents awaiting your signature, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Boldsign logoBoldsign
Oauth2

Boldsign is a digital eSignature platform for sending, signing, and tracking documents online. Organizations use it to automate agreements and manage legally binding workflows efficiently.

14 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Boldsign account to Claude via Composio Connect, enabling it to send a contract to client for signature, list all documents awaiting your signature, download signed agreement from this week, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Boldsign with

OpenAI Agents SDKClaude Agent SDKClaude CodeCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

Connecting Boldsign to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Boldsign account

Back in Claude, ask it to connect to Boldsign or give it any Boldsign-related task.

For example, ask Claude to:

  • "Send a contract to client for signature"
  • "List all documents awaiting your signature"
  • "Download signed agreement from this week"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Boldsign account is ready to use.

What is the Boldsign Claude Connector, and what's possible with it?

The Boldsign MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Boldsign account. It provides structured and secure access to your eSignature workflows, so your agent can help create, manage, and automate digital signing processes for your documents, contracts, and forms.

  • Seamless document sending and signature requests: Enable your agent to prepare documents and initiate signature requests, ensuring fast and compliant eSigning experiences for your clients or team members.
  • Automated contract management: Let your agent track the status of sent documents, follow up on pending signatures, and manage completed agreements all in one place.
  • Secure workflow automation: Allow your agent to integrate eSignature steps into broader business processes, reducing manual intervention and boosting efficiency.
  • Real-time status monitoring: Have your agent monitor and report on document progress, so you always know who has signed and who still needs to take action.
  • Centralized record keeping: Ensure your signed documents are stored and organized for easy retrieval, compliance, and auditing, all via your agent.

Troubleshooting

1. Why does Claude not use the Composio connector for Boldsign?

The connector can show as connected, but Claude must use it in each Boldsign conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Boldsign again.

2. Why does Claude show an MCP server error before Boldsign connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Boldsign.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Boldsign.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Boldsign authorization link not work?

The Composio connector is one server. Your Boldsign account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Boldsign connection.
  • Composio creates a fresh Boldsign authorization link.
  • Open that link in your browser and finish the Boldsign sign-in.

4. Why do Boldsign actions fail after they worked before?

The Boldsign connection can expire or lose permission.

  • Ask Claude to inspect the Boldsign connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Boldsign account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Boldsign.
  • If the action still fails with a permission error, check that the connected account has that permission in Boldsign itself.

5. How do I switch to a different Boldsign account?

Claude can manage the Boldsign connection for you.

  • Ask Claude to disconnect or delete the current Boldsign account.
  • Ask Claude to connect Boldsign again.
  • Open the new Composio authorization link for Boldsign.
  • Sign in with the other Boldsign account in the browser.
  • After the account connects, ask Claude to retry the Boldsign task.

6. Why is my Boldsign connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Boldsign connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Boldsign tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Boldsign.
TOOLS

Supported Tools

Every Boldsign action and event your agent gets out of the box.

Get Brand Details

Tool to get brand details by brand ID.

List Brands

Tool to list all brands in the account.

Create Custom Field

Tool to create a brand-scoped custom field.

Edit Custom Field

Tool to edit an existing custom field.

List Behalf Documents

Tool to list documents sent on behalf of users.

Edit Document (Beta)

Tool to edit a draft or sent document.

Extend Document Expiry

Tool to extend a document's expiry date.

List Documents

Tool to list documents in My Documents with filters.

Remove Document Authentication

Tool to remove authentication from a document.

Send Document

Tool to send a document for eSignature.

List Team Documents

Tool to list team documents.

Create Embedded Request Link

Tool to create an embedded request link.

Upload File (Helper)

Helper action to upload a file to R2 temp via the Composio file pipeline, returning a key that can be passed to FileUploadable fields in other actions (e.

Get API Credits Count

Tool to get remaining BoldSign API credits count.

FRAMEWORKS

How to build Boldsign MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Boldsign MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Boldsign MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Boldsign MCP with Claude Code

Codex logo

Codex

Use Boldsign MCP with Codex

OpenClaw logo

OpenClaw

Use Boldsign MCP with OpenClaw

Hermes logo

Hermes

Use Boldsign MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Boldsign MCP with Atomic Agent

Google ADK logo

Google ADK

Use Boldsign MCP with Google ADK

LangChain logo

LangChain

Use Boldsign MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Boldsign MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Boldsign MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Boldsign MCP with LlamaIndex

CrewAI logo

CrewAI

Use Boldsign MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Boldsign MCP with Pydantic AI

AutoGen logo

AutoGen

Use Boldsign MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Boldsign MCP server, the agents and LLMs can only access a fixed set of Boldsign tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Boldsign and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Boldsign tools.

Yes, absolutely. You can configure which Boldsign scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Boldsign data and credentials are handled as safely as possible.

Start with Boldsign.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Boldsign tool your agent needs.Free to start.

Start building