# How to integrate Docuseal MCP with OpenAI Agents SDK

```json
{
  "title": "How to integrate Docuseal MCP with OpenAI Agents SDK",
  "toolkit": "Docuseal",
  "toolkit_slug": "docuseal",
  "framework": "OpenAI Agents SDK",
  "framework_slug": "open-ai-agents-sdk",
  "url": "https://composio.dev/toolkits/docuseal/framework/open-ai-agents-sdk",
  "markdown_url": "https://composio.dev/toolkits/docuseal/framework/open-ai-agents-sdk.md",
  "updated_at": "2026-05-12T10:09:26.571Z"
}
```

## Introduction

This guide walks you through connecting Docuseal to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Docuseal agent that can list all document templates in your account, create a new template from html content, start a signature workflow from a pdf file through natural language commands.
This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Docuseal account through Composio's Docuseal MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Docuseal with

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

## 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 Docuseal
- Configure an AI agent that can use Docuseal as a tool
- Run a live chat session where you can ask the agent to perform Docuseal 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 Docuseal MCP server, and what's possible with it?

The Docuseal MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Docuseal account. It provides structured and secure access to your eSignature workflows, so your agent can manage templates, automate document submissions, handle submitters, and streamline template operations for you.
- Seamless template management: Effortlessly list, retrieve, update, archive, clone, or merge document templates, making it easy to organize and reuse signature documents.
- Automated submission workflows: Instantly create new submissions from uploaded PDFs, initiate signature processes, and keep tabs on all current and past document submissions.
- Direct HTML-to-template creation: Enable your agent to generate reusable document templates straight from HTML content—no manual web interface required.
- Submitter roster management: Retrieve comprehensive lists of all document submitters for reporting, tracking, or management purposes with a single request.
- Template merging and duplication: Combine multiple templates into a single document or duplicate templates to accelerate document preparation for recurring workflows.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `DOCUSEAL_ARCHIVE_SUBMISSION` | Archive Submission | Tool to archive a submission by its unique identifier. Archived submissions are not permanently deleted and can be restored. |
| `DOCUSEAL_ARCHIVE_TEMPLATE` | Archive Template | Tool to archive a specific template by its unique identifier. Use after verifying the template ID. |
| `DOCUSEAL_CLONE_TEMPLATE2` | Clone Template (v2) | Tool to clone an existing template into a new template with optional custom name, folder, and external_id. Use when you need to duplicate a template with specific customization options. |
| `DOCUSEAL_CREATE_SUBMISSION` | Create Submission | Tool to create signature requests (submissions) from an existing document template and send them to submitters. Use this when you have a pre-configured template and want to send it for signing to one or more parties. Supports email and SMS notifications, custom messages, field pre-filling, and sequential or simultaneous signing workflows. |
| `DOCUSEAL_CREATE_SUBMISSION_FROM_DOCX` | Create Submission From DOCX | Tool to create a one-off submission (signature request) from a DOCX document with dynamic content variables. Use [[variable_name]] text tags in the DOCX to define dynamic content variables and {{Field Name;role=Signer1;type=date}} text tags to define fillable fields. This allows you to generate personalized documents with pre-filled content and signature fields extracted from the DOCX file. |
| `DOCUSEAL_CREATE_SUBMISSION_FROM_HTML` | Create Submission From HTML | Tool to create a one-off submission request from HTML content with embedded field tags rendered as a fillable and signable form. Use this when you want to create a signature request directly from HTML without first creating a reusable template. Field tags in HTML (like {{field_name}} or ) will be automatically converted to fillable form fields. |
| `DOCUSEAL_CREATE_SUBMISSION_FROM_PDF` | Create Submission From PDF | Tool to create a one-off submission (signature request) from a PDF file. Use this to upload a PDF document and send it for electronic signature without creating a reusable template first. You can define signature fields and other form fields either by using text tags in the PDF (e.g., {{Signature;role=First Party;type=signature}}) or by specifying field coordinates in the request. |
| `DOCUSEAL_CREATE_SUBMISSIONS_FROM_EMAILS` | Create Submissions From Emails | Tool to create submissions for a document template and send them to specified email addresses. Use this for simplified submission creation with Zapier or other automation tools. Each email address will receive a unique submission link. |
| `DOCUSEAL_CREATE_TEMPLATE_FROM_DOCX` | Create Template from DOCX | Tool to create a fillable document template from a Microsoft Word DOCX file. Use when you need to convert a DOCX document with field tags into a template. |
| `DOCUSEAL_CREATE_TEMPLATE_FROM_HTML` | Create Template from HTML | Tool to create a fillable document template from HTML content with pre-defined fields. Use when you need to create a template directly from HTML with custom field tags for text, signatures, dates, and other fillable elements. |
| `DOCUSEAL_CREATE_TEMPLATE_FROM_PDF` | Create Template From PDF | Tool to create a fillable document template from a PDF file. Use when you need to create a reusable template from a PDF. Fields can be defined using {{Field Name;role=Signer1;type=date}} text tags in the PDF or by specifying pixel coordinates. |
| `DOCUSEAL_GET_SUBMISSION` | Get Submission | Tool to retrieve detailed information about a specific submission. Use when you need to fetch complete submission details including submitters, documents, status, template, events, and metadata. |
| `DOCUSEAL_GET_SUBMISSION_DOCUMENTS` | Get Submission Documents | Tool to retrieve documents for a submission. Returns partially filled documents if the submission is in progress, or final signed documents if completed. Use when you need to download submission documents. |
| `DOCUSEAL_GET_SUBMITTER` | Get Submitter | Tool to retrieve detailed information about a submitter by ID. Use when you need to fetch submitter details including documents, field values filled by the signer, submission events, and status. |
| `DOCUSEAL_GET_TEMPLATE` | Get Template | Tool to retrieve details of a specific template by its unique identifier. Use when you need to fetch template metadata by ID. |
| `DOCUSEAL_LIST_SUBMISSIONS` | List Submissions | List document submissions with filtering and cursor-based pagination. Use to retrieve, search, and browse existing submissions by template, status, or submitter details. Supports searching by submitter name, email, or phone. |
| `DOCUSEAL_LIST_SUBMITTERS` | List Submitters | Retrieve a paginated list of submitters with optional filtering. Use this tool to: - List all submitters across all submissions - Filter submitters by submission, status dates, or search query - Paginate through large result sets using 'after' and 'before' cursors Examples: - List all submitters: {} - Filter by submission: {"submission_id": 12345} - Search by email: {"q": "john@example.com"} - Get completed submitters in a date range: {"completed_after": "2024-01-01T00:00:00Z", "completed_before": "2024-12-31T23:59:59Z"} - Paginate results: {"limit": 50, "after": 3567000} |
| `DOCUSEAL_LIST_TEMPLATES2` | List Templates (Enhanced) | Tool to retrieve a list of available document templates with pagination and filtering. Use when you need to search templates by name, slug, external_id, folder, or archived status. |
| `DOCUSEAL_MERGE_TEMPLATES` | Merge Templates | Merge multiple DocuSeal templates into a single combined template. This action consolidates documents and fields from multiple source templates into one new template. Use this when you need to create a combined document package from existing templates. The merged template will contain all documents and fields from the source templates. Requires at least one template ID, but typically used with two or more. |
| `DOCUSEAL_UPDATE_SUBMITTER` | Update Submitter | Tool to update submitter details, pre-fill or update field values, re-send signature request emails, or mark as auto-signed for automatic signing via API. Use when you need to modify submitter information, resend requests, or programmatically complete submissions. |
| `DOCUSEAL_UPDATE_TEMPLATE2` | Update Template | Tool to update a document template by moving it to a different folder, changing its name, updating submitter roles, or unarchiving it. Use when you need to modify template properties. |
| `DOCUSEAL_UPDATE_TEMPLATE_DOCUMENTS` | Update Template Documents | Tool to add, remove, or replace documents in a template with provided PDF/DOCX file or HTML content. Use when you need to modify the document structure of an existing template. |

## Supported Triggers

None listed.

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

The Docuseal MCP server is an implementation of the Model Context Protocol that connects your AI agent to Docuseal. It provides structured and secure access so your agent can perform Docuseal 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:
- Composio API Key and OpenAI API Key
- Primary know-how of OpenAI Agents SDK
- A live Docuseal project
- Some knowledge of Python or Typescript

### 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).
- Go to Settings and copy your API key.

### 2. Install dependencies

Install the Composio SDK and the OpenAI Agents SDK.
```python
pip install composio_openai_agents openai-agents python-dotenv
```

```typescript
npm install @composio/openai-agents @openai/agents dotenv
```

### 3. Set up environment variables

Create a .env file and add your OpenAI and Composio API keys.
```bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com
```

### 4. Import dependencies

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 Docuseal.
```python
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
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
```

### 5. Set up the Composio instance

No description provided.
```python
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())
```

```typescript
dotenv.config();

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

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
```

### 6. Create a Tool Router session

What is happening:
- You give the Tool Router the user id and the toolkits you want available. Here, it is only docuseal.
- The router checks the user's Docuseal connection and prepares the MCP endpoint.
- The returned session.mcp.url is the MCP URL that your agent will use to access Docuseal.
- This approach keeps things lightweight and lets the agent request Docuseal tools only when needed during the conversation.
```python
# Create a Docuseal Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["docuseal"]
)

mcp_url = session.mcp.url
```

```typescript
// Create Tool Router session for Docuseal
const session = await composio.create(userId as string, {
  toolkits: ['docuseal'],
});
const mcpUrl = session.mcp.url;
```

### 7. Configure the agent

No description provided.
```python
# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Docuseal. "
        "Help users perform Docuseal 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",
            }
        )
    ],
)
```

```typescript
// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Docuseal. Help users perform Docuseal operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
```

### 8. Start chat loop and handle conversation

No description provided.
```python
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())
```

```typescript
// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

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

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

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

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

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

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

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

## Complete Code

```python
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=["docuseal"]
)
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 Docuseal. "
        "Help users perform Docuseal 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())
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

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

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['docuseal'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Docuseal. Help users perform Docuseal operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

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

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

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

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

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

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\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

This was a starter code for integrating Docuseal MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Docuseal.
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 Docuseal MCP Agent with another framework

- [Claude Agent SDK](https://composio.dev/toolkits/docuseal/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/docuseal/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/docuseal/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/docuseal/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/docuseal/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/docuseal/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/docuseal/framework/cli)
- [Google ADK](https://composio.dev/toolkits/docuseal/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/docuseal/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/docuseal/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/docuseal/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/docuseal/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/docuseal/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.
- [Boldsign](https://composio.dev/toolkits/boldsign) - 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.
- [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.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Docuseal MCP?

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

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

Yes, absolutely. You can configure which Docuseal 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 Docuseal data and credentials are handled as safely as possible.

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