How to integrate Boldsign MCP with Claude Code

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Boldsign logo
Claude Code logo
divider

Introduction

Manage your Boldsign directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Boldsign with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Boldsign to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

Supported Tools & Triggers

Tools
Get Brand DetailsTool to get brand details by brand ID.
List BrandsTool to list all brands in the account.
Create Custom FieldTool to create a brand-scoped custom field.
Edit Custom FieldTool to edit an existing custom field.
List Behalf DocumentsTool to list documents sent on behalf of users.
Edit Document (Beta)Tool to edit a draft or sent document.
Extend Document ExpiryTool to extend a document's expiry date.
List DocumentsTool to list documents in My Documents with filters.
Remove Document AuthenticationTool to remove authentication from a document.
Send DocumentTool to send a document for eSignature.
List Team DocumentsTool to list team documents.
Create Embedded Request LinkTool 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 CountTool to get remaining BoldSign API credits count.

What is the Boldsign MCP server, 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.

Connecting Boldsign via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Boldsign) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Boldsign account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["boldsign"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http boldsign-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Boldsign. This URL will be used to connect Claude Code to Boldsign.

What's happening:
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Boldsign
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Boldsign MCP to Claude Code

bash
claude mcp add --transport http boldsign-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (boldsign-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Boldsign MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your boldsign-composio entry in the list
  • This confirms that Claude Code can now access Boldsign tools

If everything is wired up, you should see your boldsign-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Boldsign

The first time you try to use Boldsign tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Boldsign
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Boldsign authorization flow
  • Return to the terminal and start using Boldsign through Claude Code

Once authenticated, you can ask Claude Code to perform Boldsign operations in natural language. For example:

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

Complete Code

Here's the complete code to get you started with Boldsign and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["boldsign"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http boldsign-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Boldsign with Claude Code using Composio's MCP server. Now you can interact with Boldsign directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Boldsign operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Boldsign operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

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 Cowork logo

Claude Cowork

Use Boldsign MCP with Claude Cowork

Codex logo

Codex

Use Boldsign MCP with Codex

OpenClaw logo

OpenClaw

Use Boldsign MCP with OpenClaw

Hermes logo

Hermes

Use Boldsign MCP with Hermes

CLI logo

CLI

Use Boldsign MCP with CLI

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

FAQ

What are the differences in Tool Router MCP and Boldsign MCP?

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.

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code 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.

Can I manage the permissions and scopes for Boldsign while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗