How to integrate Documenso MCP with CrewAI

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Documenso logo
CrewAI logo
divider

Introduction

This guide walks you through connecting Documenso to CrewAI using the Composio tool router. By the end, you'll have a working Documenso agent that can send a contract to client for signature, download the latest signed nda document, list all templates for onboarding paperwork through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Documenso account through Composio's Documenso MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Documenso with

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Documenso connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Documenso
  • Build a conversational loop where your agent can execute Documenso 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 Documenso MCP server, and what's possible with it?

The Documenso MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Documenso account. It provides structured and secure access to your electronic signature workflows, so your agent can create documents, distribute them for signing, manage templates, and download signed files automatically on your behalf.

  • Automated document creation and duplication: Prompt your agent to generate new documents or make exact copies of existing ones for rapid workflow setup.
  • Seamless document distribution for signatures: Let your agent send documents to one or more recipients, kicking off secure e-signature flows without manual intervention.
  • Template management and retrieval: Ask your agent to list, fetch, or delete document templates, keeping your signing processes organized and up-to-date.
  • Download and access signed documents: Have your agent retrieve finalized, signed PDFs automatically for seamless archiving or sharing.
  • Streamlined document organization: Direct your agent to move documents between personal and team spaces, or remove unnecessary fields to keep everything tidy and current.

Supported Tools & Triggers

Tools
Create Document BetaTool to create a new document using the beta endpoint that returns a presigned URL for file upload.
Create Document FieldTool to create a single field for a document.
Create Document Fields (Bulk)Tool to create multiple fields on a document in a single operation.
Create Document RecipientTool to create a single recipient for a document.
Create Document Recipients BulkTool to create multiple recipients for a document at once.
Create Embedding Presign Token V2 BetaCreate a presign token for Documenso embedded authoring sessions.
Create EnvelopeTool to create a new envelope in Documenso.
Create Envelope AttachmentCreate a new attachment for an envelope in Documenso.
Create Envelope Items BulkTool to create multiple items for an envelope with optional file attachments.
Create Envelope Recipients BulkTool to create multiple recipients for an envelope in bulk.
Create FolderCreate a new folder in Documenso to organize documents or templates.
Create Template BetaTool to create a new template using the beta endpoint that returns a presigned URL for file upload.
Create Template FieldTool to create a single field for a template.
Create Template Fields (Bulk)Tool to create multiple fields on a template in a single operation.
Create Template RecipientTool to create a single recipient for a template.
Create Template Recipients BulkTool to create multiple recipients for a template at once.
Delete DocumentTool to delete a document.
Delete Document AttachmentTool to delete an attachment from a document.
Delete Document FieldTool to delete a single document field by ID.
Delete Document FieldsTool to delete one or more fields from a document.
Delete Document RecipientTool to delete a recipient from a document.
Delete EnvelopeTool to permanently delete an envelope.
Delete Envelope AttachmentTool to delete an attachment from an envelope.
Delete Envelope FieldTool to delete a field from an envelope.
Delete Envelope ItemTool to delete an item from an envelope.
Delete Envelope RecipientTool to delete a recipient from an envelope.
Delete FolderTool to permanently delete a folder.
Delete TemplatePermanently delete a template by its ID.
Delete Template Direct LinkDelete a direct link for a template.
Delete Template RecipientTool to delete a recipient from a template.
Delete Template V2Tool to permanently delete a template using the v2 API.
Distribute Document V2Tool to distribute a document for signing.
Distribute EnvelopeTool to distribute an envelope to recipients for signing.
Download Envelope ItemDownload an envelope item as PDF.
Download Signed DocumentDownload a completed/signed document as PDF.
Duplicate Document V2Tool to duplicate a document.
Duplicate Envelope V2Tool to duplicate an envelope with all its settings.
Duplicate TemplateTool to duplicate a template with all its settings.
Find DocumentsFind documents based on search criteria with filtering and pagination.
Find Documents V2Retrieve a paginated list of documents with optional filtering and sorting.
Find EnvelopesTool to find envelopes based on search criteria, filters, and pagination.
Find FoldersTool to find folders based on search criteria and filters.
Find TemplatesRetrieve a paginated list of templates with optional filtering and search.
Get Document By IDRetrieve complete information about a document by its ID.
Get Document FieldTool to retrieve a document field by its ID.
Get Document RecipientTool to retrieve detailed information about a document recipient by their ID.
Get Documents By IDsRetrieve multiple documents by their IDs in a single request.
Get Envelope AttachmentTool to find all attachments for a specific envelope.
Get Envelope Audit LogTool to retrieve audit logs for an envelope.
Get Envelope By IDRetrieve complete information about an envelope by its ID.
Get Envelope FieldTool to fetch an envelope field by ID.
Get Envelope RecipientTool to retrieve detailed information about an envelope recipient by their ID.
Get Envelopes By IDsTool to retrieve multiple envelopes by their IDs.
Get Template By IDRetrieve complete information about a template by its ID.
Get Template FieldTool to fetch a template field by ID.
Get Template RecipientTool to retrieve detailed information about a template recipient by their ID.
Get Templates By IDsRetrieve multiple templates by their IDs in a single request.
List TemplatesTool to list templates.
Move Document V2Tool to move a document to a team.
Redistribute Document V2Re-send signing request emails to specified recipients of a document.
Redistribute EnvelopeTool to redistribute an envelope to recipients who have not actioned it.
Remove Team Member V1Remove a member from a Documenso team.
Update Document AttachmentTool to update an existing document attachment.
Update Document FieldTool to update a single document field's properties in Documenso v2 API.
Update Document Fields BulkTool to update multiple document fields in a single operation.
Update Document Recipient V2Tool to update a document recipient using the v2 API.
Update Document V2Update document properties like title, visibility, and signing settings.
Update EnvelopeUpdate envelope properties like title, visibility, and signing settings.
Update Envelope AttachmentTool to update an existing envelope attachment.
Update Envelope Fields BulkTool to update multiple envelope fields in a single request.
Update Envelope Items BulkTool to update multiple envelope items in a single request.
Update FolderUpdate properties of an existing folder including name, pinned status, parent folder, and visibility.
Update TemplateUpdate template properties like title, visibility, and signing settings.
Update Template Fields BulkTool to update multiple template fields in a single operation.
Update Template RecipientTool to update a template recipient.
Update Template Recipients BulkTool to update multiple template recipients in a single API call.
Use Template (v2-beta)Tool to create a document from a template.

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

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Documenso connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python

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.

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Documenso via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env

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_here

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

Import dependencies

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")
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 Documenso MCP URL

Create a Composio Tool Router session for Documenso

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["documenso"])

url = session.mcp.url
What's happening:
  • You create a Documenso only session through Composio
  • Composio returns an MCP HTTP URL that exposes Documenso tools

Initialize the MCP Server

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,
    )
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.

Create a CLI Chatloop and define the Crew

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")
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.

Complete Code

Here's the complete code to get you started with Documenso and CrewAI:

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=["documenso"],
)
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 Documenso through Composio's Tool Router. The agent can perform Documenso 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 Documenso MCP Agent with another framework

FAQ

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

With a standalone Documenso MCP server, the agents and LLMs can only access a fixed set of Documenso tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Documenso 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 Documenso tools.

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

Yes, absolutely. You can configure which Documenso 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 Documenso 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.