# How to integrate Boldsign MCP with LangChain

```json
{
  "title": "How to integrate Boldsign MCP with LangChain",
  "toolkit": "Boldsign",
  "toolkit_slug": "boldsign",
  "framework": "LangChain",
  "framework_slug": "langchain",
  "url": "https://composio.dev/toolkits/boldsign/framework/langchain",
  "markdown_url": "https://composio.dev/toolkits/boldsign/framework/langchain.md",
  "updated_at": "2026-05-12T10:03:25.712Z"
}
```

## Introduction

This guide walks you through connecting Boldsign to LangChain using the Composio tool router. By the end, you'll have a working Boldsign agent that can send a contract to client for signature, list all documents awaiting your signature, download signed agreement from this week through natural language commands.
This guide will help you understand how to give your LangChain agent real control over a Boldsign account through Composio's Boldsign MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Boldsign with

- [OpenAI Agents SDK](https://composio.dev/toolkits/boldsign/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/boldsign/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/boldsign/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/boldsign/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/boldsign/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/boldsign/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/boldsign/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/boldsign/framework/cli)
- [Google ADK](https://composio.dev/toolkits/boldsign/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/boldsign/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/boldsign/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/boldsign/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/boldsign/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Connect your Boldsign project to Composio
- Create a Tool Router MCP session for Boldsign
- Initialize an MCP client and retrieve Boldsign tools
- Build a LangChain agent that can interact with Boldsign
- Set up an interactive chat interface for testing

## What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.
Key features include:
- Agent Framework: Build agents that can use tools and make decisions
- MCP Integration: Connect to external services through Model Context Protocol adapters
- Memory Management: Maintain conversation history across interactions
- Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

## 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.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `BOLDSIGN_BRAND_GET` | Get Brand Details | Tool to get brand details by brand ID. Use after obtaining the brand identifier. |
| `BOLDSIGN_BRAND_LIST` | List Brands | Tool to list all brands in the account. Use after confirming account is authenticated. |
| `BOLDSIGN_CUSTOM_FIELD_CREATE` | Create Custom Field | Tool to create a brand-scoped custom field. Use when you need to define and register a new custom field for a specific brand. |
| `BOLDSIGN_CUSTOM_FIELD_EDIT` | Edit Custom Field | Tool to edit an existing custom field. Use when you need to update a custom field's properties after creation. |
| `BOLDSIGN_DOCUMENT_BEHALF_LIST` | List Behalf Documents | Tool to list documents sent on behalf of users. Use when fetching and filtering documents you've sent or on behalf of others. |
| `BOLDSIGN_DOCUMENT_EDIT_BETA` | Edit Document (Beta) | Tool to edit a draft or sent document. Use when updating files, recipients, or document settings before finalizing the document. |
| `BOLDSIGN_DOCUMENT_EXTEND_EXPIRY` | Extend Document Expiry | Tool to extend a document's expiry date. Use before signing to prolong a document's deadline. |
| `BOLDSIGN_DOCUMENT_LIST` | List Documents | Tool to list documents in My Documents with filters. Use when you need to fetch and filter documents based on various criteria. |
| `BOLDSIGN_DOCUMENT_REMOVE_AUTHENTICATION` | Remove Document Authentication | Tool to remove authentication from a document. Use when you need to disable signer authentication on an existing document before the signing process. |
| `BOLDSIGN_DOCUMENT_SEND` | Send Document | Tool to send a document for eSignature. Use when you need to deliver documents to recipients for signing. |
| `BOLDSIGN_DOCUMENT_TEAM_LIST` | List Team Documents | Tool to list team documents. Use when a team or account admin needs to retrieve all team documents with optional filters. |
| `BOLDSIGN_EMBEDDED_REQUEST_CREATE_LINK` | Create Embedded Request Link | Tool to create an embedded request link. Use after specifying title and signers to generate an embeddable URL for in-app document preparation and sending. |
| `BOLDSIGN_FILE_UPLOAD` | 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.g., BrandLogo in brand create). |
| `BOLDSIGN_PLAN_GET_API_CREDITS_COUNT` | Get API Credits Count | Tool to get remaining BoldSign API credits count. Use after authenticating your BoldSign account. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Boldsign MCP server is an implementation of the Model Context Protocol that connects your AI agent to Boldsign. It provides structured and secure access so your agent can perform Boldsign operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

No description provided.

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

No description provided.
```python
pip install composio-langchain langchain-mcp-adapters langchain python-dotenv
```

```typescript
npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates your requests to Composio's API
- COMPOSIO_USER_ID identifies the user for session management
- OPENAI_API_KEY enables access to OpenAI's language models
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

No description provided.
```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
```

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
```

### 5. Initialize Composio client

What's happening:
- We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
- Creating a Composio instance that will manage our connection to Boldsign tools
- Validating that COMPOSIO_USER_ID is also set before proceeding
```python
async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
```

```typescript
const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
```

### 6. Create a Tool Router session

What's happening:
- We're creating a Tool Router session that gives your agent access to Boldsign tools
- The create method takes the user ID and specifies which toolkits should be available
- The returned session.mcp.url is the MCP server URL that your agent will use
- This approach allows the agent to dynamically load and use Boldsign tools as needed
```python
# Create Tool Router session for Boldsign
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['boldsign']
)

url = session.mcp.url
```

```typescript
const session = await composio.create(
    userId as string,
    {
        toolkits: ['boldsign']
    }
);

const url = session.mcp.url;
```

### 7. Configure the agent with the MCP URL

No description provided.
```python
client = MultiServerMCPClient({
    "boldsign-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
```

```typescript
const client = new MultiServerMCPClient({
    "boldsign-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
```

### 8. Set up interactive chat interface

No description provided.
```python
conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Boldsign related question or task to the agent.\n")

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
```

```typescript
let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Boldsign related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
```

### 9. Run the application

No description provided.
```python
if __name__ == "__main__":
    asyncio.run(main())
```

```typescript
main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
```

## Complete Code

```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['boldsign']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "boldsign-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Boldsign related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

if __name__ == "__main__":
    asyncio.run(main())
```

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['boldsign']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "boldsign-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Boldsign related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
```

## Conclusion

You've successfully built a LangChain agent that can interact with Boldsign through Composio's Tool Router.
Key features of this implementation:
- Dynamic tool loading through Composio's Tool Router
- Conversation history maintenance for context-aware responses
- Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

## How to build Boldsign MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/boldsign/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/boldsign/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/boldsign/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/boldsign/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/boldsign/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/boldsign/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/boldsign/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/boldsign/framework/cli)
- [Google ADK](https://composio.dev/toolkits/boldsign/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/boldsign/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/boldsign/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/boldsign/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/boldsign/framework/crew-ai)

## Related Toolkits

- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.
- [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.
- [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.
- [Affinda](https://composio.dev/toolkits/affinda) - Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data.
- [Agility cms](https://composio.dev/toolkits/agility_cms) - Agility CMS is a headless content management system for building and managing digital experiences across platforms. It lets teams update content quickly and deliver omnichannel experiences with ease.
- [Algodocs](https://composio.dev/toolkits/algodocs) - Algodocs is an AI-powered platform that automates data extraction from business documents. It delivers fast, secure, and accurate processing without templates or manual training.
- [Api2pdf](https://composio.dev/toolkits/api2pdf) - Api2Pdf is a REST API for generating PDFs from HTML, URLs, and documents using powerful engines like wkhtmltopdf and Headless Chrome. It streamlines document conversion and automation for developers and businesses.
- [Aryn](https://composio.dev/toolkits/aryn) - Aryn is an AI-powered platform for parsing, extracting, and analyzing data from unstructured documents. Use it to automate document processing and unlock actionable insights from your files.
- [Boloforms](https://composio.dev/toolkits/boloforms) - BoloForms is an eSignature platform built for small businesses, offering unlimited signatures, templates, and forms. It simplifies digital document signing and team collaboration at a predictable, fixed price.
- [Box](https://composio.dev/toolkits/box) - Box is a cloud content management and file sharing platform for businesses. It helps teams securely store, organize, and collaborate on files from anywhere.
- [Carbone](https://composio.dev/toolkits/carbone) - Carbone is a blazing-fast report generator that turns JSON data into PDFs, Word docs, spreadsheets, and more using flexible templates. It lets you automate document creation at scale with minimal code.
- [Castingwords](https://composio.dev/toolkits/castingwords) - CastingWords is a transcription service specializing in human-powered, accurate transcripts via a simple API. Get seamless audio-to-text conversion for interviews, meetings, podcasts, and more.
- [Cloudconvert](https://composio.dev/toolkits/cloudconvert) - CloudConvert is a powerful file conversion service supporting over 200 file formats. It streamlines converting, compressing, and managing documents, media, and more, all in one place.
- [Cloudlayer](https://composio.dev/toolkits/cloudlayer) - Cloudlayer is a document and asset generation service for creating PDFs and images via API or SDKs. It lets you automate high-quality doc creation, saving dev time and reducing manual work.
- [Cloudpress](https://composio.dev/toolkits/cloudpress) - Cloudpress is a content export tool for Google Docs and Notion. It automates publishing to your favorite Content Management Systems.
- [Contentful graphql](https://composio.dev/toolkits/contentful_graphql) - Contentful graphql is a content delivery API that lets you access Contentful data using GraphQL queries. It gives you efficient, flexible ways to fetch and manage structured content for any digital project.
- [Conversion tools](https://composio.dev/toolkits/conversion_tools) - Conversion Tools is an online service for converting documents between formats such as PDF, Word, Excel, XML, and CSV. It lets you automate complex document workflows with just a few clicks.
- [Convertapi](https://composio.dev/toolkits/convertapi) - ConvertAPI is a robust file conversion service for documents, images, and spreadsheets. It streamlines programmatic format changes and lets developers automate complex workflows with a single API.
- [Craftmypdf](https://composio.dev/toolkits/craftmypdf) - CraftMyPDF is a web-based service for designing and generating PDFs with templates and live data. It streamlines document creation by automating personalized PDFs at scale.
- [Docmosis](https://composio.dev/toolkits/docmosis) - Docmosis generates PDF and Word documents from user-defined templates. It's perfect for merging data fields to quickly produce reports, invoices, and business letters.

## Frequently Asked Questions

### 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 LangChain?

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

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)