# How to integrate Boldsign MCP with CrewAI ```json { "title": "How to integrate Boldsign MCP with CrewAI", "toolkit": "Boldsign", "toolkit_slug": "boldsign", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/boldsign/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/boldsign/framework/crew-ai.md", "updated_at": "2026-05-12T10:03:25.712Z" } ``` ## Introduction This guide walks you through connecting Boldsign to CrewAI 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 CrewAI 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) - [LangChain](https://composio.dev/toolkits/boldsign/framework/langchain) - [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) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Boldsign connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Boldsign - Build a conversational loop where your agent can execute Boldsign operations ## What is CrewAI? CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews. Key features include: - Agent Roles: Define specialized agents with specific goals and backstories - Task Management: Create tasks with clear descriptions and expected outputs - Crew Orchestration: Combine agents and tasks into collaborative workflows - MCP Integration: Connect to external tools through Model Context Protocol ## 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 Before starting, make sure you have: - Python 3.9 or higher - A Composio account and API key - A Boldsign connection authorized in Composio - An OpenAI API key for the CrewAI LLM - Basic familiarity with Python ### 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 **What's happening:** - composio connects your agent to Boldsign via MCP - crewai provides Agent, Task, Crew, and LLM primitives - crewai-tools[mcp] includes MCP helpers - python-dotenv loads environment variables from .env ```bash pip install composio crewai crewai-tools[mcp] python-dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates with Composio - USER_ID scopes the session to your account - OPENAI_API_KEY lets CrewAI use your chosen OpenAI model ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import dependencies **What's happening:** - CrewAI classes define agents and tasks, and run the workflow - MCPServerHTTP connects the agent to an MCP endpoint - Composio will give you a short lived Boldsign MCP URL ```python import os from composio import Composio from crewai import Agent, Task, Crew from crewai_tools import MCPServerAdapter import dotenv dotenv.load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set") ``` ### 5. Create a Composio Tool Router session for Boldsign **What's happening:** - You create a Boldsign only session through Composio - Composio returns an MCP HTTP URL that exposes Boldsign tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["boldsign"]) url = session.mcp.url ``` ### 6. Initialize the MCP Server **What's Happening:** - Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication. - MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format. - Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools. - Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops. - Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries. ```python server_params = { "url": url, "transport": "streamable-http", "headers": {"x-api-key": COMPOSIO_API_KEY}, } with MCPServerAdapter(server_params) as tools: agent = Agent( role="Search Assistant", goal="Help users search the internet effectively", backstory="You are a helpful assistant with access to search tools.", tools=tools, verbose=False, max_iter=10, ) ``` ### 7. Create a CLI Chatloop and define the Crew **What's Happening:** - Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable. - Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean. - Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses. - Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context. - Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response. - Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity. ```python print("Chat started! Type 'exit' or 'quit' to end.\n") conversation_context = "" while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue conversation_context += f"\nUser: {user_input}\n" print("\nAgent is thinking...\n") task = Task( description=( f"Conversation history:\n{conversation_context}\n\n" f"Current request: {user_input}" ), expected_output="A helpful response addressing the user's request", agent=agent, ) crew = Crew(agents=[agent], tasks=[task], verbose=False) result = crew.kickoff() response = str(result) conversation_context += f"Agent: {response}\n" print(f"Agent: {response}\n") ``` ## Complete Code ```python from crewai import Agent, Task, Crew, LLM from crewai_tools import MCPServerAdapter from composio import Composio from dotenv import load_dotenv import os load_dotenv() GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") # Initialize Composio and create a session composio = Composio(api_key=COMPOSIO_API_KEY) session = composio.create( user_id=COMPOSIO_USER_ID, toolkits=["boldsign"], ) url = session.mcp.url # Configure LLM llm = LLM( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY"), ) server_params = { "url": url, "transport": "streamable-http", "headers": {"x-api-key": COMPOSIO_API_KEY}, } with MCPServerAdapter(server_params) as tools: agent = Agent( role="Search Assistant", goal="Help users with internet searches", backstory="You are an expert assistant with access to Composio Search tools.", tools=tools, llm=llm, verbose=False, max_iter=10, ) print("Chat started! Type 'exit' or 'quit' to end.\n") conversation_context = "" while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue conversation_context += f"\nUser: {user_input}\n" print("\nAgent is thinking...\n") task = Task( description=( f"Conversation history:\n{conversation_context}\n\n" f"Current request: {user_input}" ), expected_output="A helpful response addressing the user's request", agent=agent, ) crew = Crew(agents=[agent], tasks=[task], verbose=False) result = crew.kickoff() response = str(result) conversation_context += f"Agent: {response}\n" print(f"Agent: {response}\n") ``` ## Conclusion You now have a CrewAI agent connected to Boldsign through Composio's Tool Router. The agent can perform Boldsign operations through natural language commands. Next steps: - Add role-specific instructions to customize agent behavior - Plug in more toolkits for multi-app workflows - Chain tasks for complex multi-step operations ## 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) - [LangChain](https://composio.dev/toolkits/boldsign/framework/langchain) - [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) ## 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 CrewAI? Yes, you can. CrewAI 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)