How to integrate Docuseal MCP with Codex

Docuseal logo
Codex logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Docuseal MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Docuseal with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Docuseal MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on dashboard.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

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 & Triggers

Tools
Archive TemplateTool to archive a specific template by its unique identifier.
Clone TemplateTool to clone an existing template by its id with a new name.
Create Submission From PDFTool to create a one-off submission from a pdf file.
Create Template from HTMLTool to create a template from html content.
Get TemplateTool to retrieve details of a specific template by its unique identifier.
List SubmissionsTool to list all document submissions with optional pagination and document filtering.
List SubmittersTool to retrieve a list of all submitters.
List TemplatesTool to retrieve a list of all templates.
Merge TemplatesTool to merge multiple templates into one with a new name.
Update TemplateTool to update details of a specific template, including name and folder.

Conclusion

You've successfully integrated Docuseal with Codex using Composio's MCP server. Now you can interact with Docuseal directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Docuseal operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Docuseal operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Docuseal MCP Agent with another framework

FAQ

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 Codex?

Yes, you can. Codex 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.

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.