How to integrate Documenso MCP with OpenAI Agents SDK

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

30 min · no commitment · see it on your stack

Documenso logo
OpenAI Agents SDK logo
divider

Introduction

This guide walks you through connecting Documenso to the OpenAI Agents SDK 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 OpenAI Agents SDK 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 and set up your OpenAI and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Documenso
  • Configure an AI agent that can use Documenso as a tool
  • Run a live chat session where you can ask the agent to perform Documenso operations

What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

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:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Documenso project
  • Some knowledge of Python or Typescript

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

Install dependencies

pip install composio_openai_agents openai-agents python-dotenv

Install the Composio SDK and the OpenAI Agents SDK.

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

Import dependencies

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Documenso.

Set up the Composio instance

load_dotenv()

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

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
What's happening:
  • load_dotenv() loads your .env file so OPENAI_API_KEY and COMPOSIO_API_KEY are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.

Create a Tool Router session

# Create a Documenso Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["documenso"]
)

mcp_url = session.mcp.url

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only documenso.
  • The router checks the user's Documenso connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Documenso.
  • This approach keeps things lightweight and lets the agent request Documenso tools only when needed during the conversation.

Configure the agent

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Documenso. "
        "Help users perform Documenso operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Documenso and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a HostedMCPTool that connects to the MCP server URL we created earlier.
  • The headers dict includes the Composio API key for secure authentication with the MCP server.
  • require_approval: 'never' means the agent can execute Documenso operations without asking for permission each time, making interactions smoother.

Start chat loop and handle conversation

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
What's happening:
  • The program prints a session URL that you visit to authorize Documenso.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using Runner.run().
  • The responses are printed to the console, and conversations are saved locally using SQLite.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Documenso and OpenAI Agents SDK:

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

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

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["documenso"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Documenso. "
        "Help users perform Documenso operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())

Conclusion

This was a starter code for integrating Documenso MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Documenso.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Documenso MCP Agent with another framework

Claude Agent SDK logo

Claude Agent SDK

Use Documenso MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Documenso MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Documenso MCP with Claude Cowork

Codex logo

Codex

Use Documenso MCP with Codex

OpenClaw logo

OpenClaw

Use Documenso MCP with OpenClaw

Hermes logo

Hermes

Use Documenso MCP with Hermes

CLI logo

CLI

Use Documenso MCP with CLI

Google ADK logo

Google ADK

Use Documenso MCP with Google ADK

LangChain logo

LangChain

Use Documenso MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Documenso MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Documenso MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Documenso MCP with LlamaIndex

CrewAI logo

CrewAI

Use Documenso MCP with CrewAI

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 OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK 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.

Get started for freeGet a demo↗