SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Boldsign MCP with Pydantic AI

Connect Pydantic AI 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

This guide walks you through connecting Boldsign to Pydantic AI using the Composio tool router. By the end, you'll have a working Boldsign agent that can send documents for signature, list and edit documents, extend document expiry, create embedded signing links, and check your API credits through natural language commands.

This guide will help you understand how to give your Pydantic AI 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

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIAutoGen

TL;DR

Here's what you'll learn:
  • How to set up your Composio API key and User ID
  • How to create a Composio Tool Router session for Boldsign
  • How to attach an MCP Server to a Pydantic AI agent
  • How to stream responses and maintain chat history
  • How to build a simple REPL-style chat interface to test your Boldsign workflows

What is Pydantic AI?

Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications.

Key features include:

  • Type Safety: Built on Pydantic for automatic data validation
  • MCP Support: Native support for Model Context Protocol servers
  • Streaming: Built-in support for streaming responses
  • Async First: Designed for async/await patterns

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

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

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account with an active API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

bash
pip install composio pydantic-ai python-dotenv

Install the required libraries.

What's happening:

  • composio connects your agent to external SaaS tools like Boldsign
  • pydantic-ai lets you create structured AI agents with tool support
  • python-dotenv loads your environment variables securely from a .env file
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your agent to Composio's API
  • USER_ID associates your session with your account for secure tool access
  • OPENAI_API_KEY to access OpenAI LLMs
5

Import dependencies

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()
What's happening:
  • We load environment variables and import required modules
  • Composio manages connections to Boldsign
  • MCPServerStreamableHTTP connects to the Boldsign MCP server endpoint
  • Agent from Pydantic AI lets you define and run the AI assistant
6

Create a Tool Router Session

python
async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Boldsign
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["boldsign"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")
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
7

Initialize the Pydantic AI Agent

python
# Attach the MCP server to a Pydantic AI Agent
boldsign_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
agent = Agent(
    "openai:gpt-5",
    toolsets=[boldsign_mcp],
    instructions=(
        "You are a Boldsign assistant. Use Boldsign tools to help users "
        "with their requests. Ask clarifying questions when needed."
    ),
)
What's happening:
  • The MCP client connects to the Boldsign endpoint
  • The agent uses GPT-5 to interpret user commands and perform Boldsign operations
  • The instructions field defines the agent's role and behavior
8

Build the chat interface

python
# Simple REPL with message history
history = []
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to help you with Boldsign.\n")

while True:
    user_input = input("You: ").strip()
    if user_input.lower() in {"exit", "quit", "bye"}:
        print("\nGoodbye!")
        break
    if not user_input:
        continue

    print("\nAgent is thinking...\n", flush=True)

    async with agent.run_stream(user_input, message_history=history) as stream_result:
        collected_text = ""
        async for chunk in stream_result.stream_output():
            text_piece = None
            if isinstance(chunk, str):
                text_piece = chunk
            elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                text_piece = chunk.delta
            elif hasattr(chunk, "text"):
                text_piece = chunk.text
            if text_piece:
                collected_text += text_piece
        result = stream_result

    print(f"Agent: {collected_text}\n")
    history = result.all_messages()
What's happening:
  • The agent reads input from the terminal and streams its response
  • Boldsign API calls happen automatically under the hood
  • The model keeps conversation history to maintain context across turns
9

Run the application

python
if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • The asyncio loop launches the agent and keeps it running until you exit

Complete Code

Here's the complete code to get you started with Boldsign and Pydantic AI:

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()

async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Boldsign
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["boldsign"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")

    # Attach the MCP server to a Pydantic AI Agent
    boldsign_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
    agent = Agent(
        "openai:gpt-5",
        toolsets=[boldsign_mcp],
        instructions=(
            "You are a Boldsign assistant. Use Boldsign tools to help users "
            "with their requests. Ask clarifying questions when needed."
        ),
    )

    # Simple REPL with message history
    history = []
    print("Chat started! Type 'exit' or 'quit' to end.\n")
    print("Try asking the agent to help you with Boldsign.\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "bye"}:
            print("\nGoodbye!")
            break
        if not user_input:
            continue

        print("\nAgent is thinking...\n", flush=True)

        async with agent.run_stream(user_input, message_history=history) as stream_result:
            collected_text = ""
            async for chunk in stream_result.stream_output():
                text_piece = None
                if isinstance(chunk, str):
                    text_piece = chunk
                elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                    text_piece = chunk.delta
                elif hasattr(chunk, "text"):
                    text_piece = chunk.text
                if text_piece:
                    collected_text += text_piece
            result = stream_result

        print(f"Agent: {collected_text}\n")
        history = result.all_messages()

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

Conclusion

You've built a Pydantic AI agent that can interact with Boldsign through Composio's Tool Router. With this setup, your agent can perform real Boldsign actions through natural language. You can extend this further by:
  • Adding other toolkits like Gmail, HubSpot, or Salesforce
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + Boldsign for workflow automation)
This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations.
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

Remove authentication for a specified signer on an existing document, with an optional signer order to distinguish roles sharing an email address.

Send Document

Tool to send a document for eSignature.

List Team Documents

List a page of team documents for a team or account admin, with optional filters.

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

Claude Code logo

Claude Code

Use Boldsign MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Boldsign MCP with Claude Cowork

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

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

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. Pydantic AI 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