How to integrate eSignatures MCP with Codex

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

eSignatures logoeSignatures
Api Key

eSignatures is an electronic signature platform for creating templates, sending contracts, and managing signers. It helps teams close agreements faster with trackable, paperless signing workflows.

28 Tools

Introduction

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

Also integrate eSignatures 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 1000+ 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 eSignatures 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 eSignatures MCP server, and what's possible with it?

The eSignatures MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your eSignatures account. It provides structured and secure access to your contract templates, contracts, signers, and signing workflows, so your agent can create and send contracts, manage signers, update content, track signing status, and organize templates on your behalf.

  • Contract creation and delivery: Have your agent create contract drafts from templates or Markdown, send them for signature, or send an existing draft when it is ready.
  • Signer management: Let the agent add, update, or remove signers from editable contracts, resend signature requests, and adjust signer contact, delivery, authentication, or redirect details.
  • Template creation and collaboration: Direct your agent to create, duplicate, rename, label, or delete reusable templates, and manage the collaborators who can edit them.
  • Contract and template editing: Instruct your agent to preview and apply exact content changes, update contract placeholder values, and review template or contract Markdown.
  • Signing workflow tracking: Have your agent check contract details, current status, signers, completed field values, and signed documents when available, or withdraw an active unsigned contract.

Conclusion

You've successfully integrated eSignatures with Codex using Composio's MCP server. Now you can interact with eSignatures 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 eSignatures operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 1000+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

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

Supported Tools

Every eSignatures action and event your agent gets out of the box.

Add Contract Signer

Add a signer to an editable contract without automatically sending a signature request.

Add Contract Signers

Add a non-empty list of signers to an editable contract by calling the provider's singular endpoint sequentially in request order.

Add Template Collaborator

Create a name-only collaborator who can edit a template.

Create and Send Contract

Create a contract from a template or from ad-hoc Markdown and immediately send signature requests to its signers.

Create Contract Draft

Create a test or production contract draft from a template or from ad-hoc Markdown, without sending signature requests or otherwise delivering it externally.

Create Template

Create a reusable Markdown contract template.

Delete Contract Signer

Permanently remove a signer from an editable contract.

Delete Template

Permanently delete a template.

Duplicate Template

Duplicate a template with a new title plus optional placeholder replacements.

Get Contract

Get one contract's current status, details, signers, signer field values, and temporary signed-PDF URL when available.

Get Contract Content

Return the Markdown content of one contract.

Get Contract Placeholder Fields

Return the current placeholder replacements for one contract.

Get Template

Get one template's metadata, placeholder keys, and signer-field IDs.

Get Template Content

Return the Markdown content of one template.

Invite Template Collaborator

Invite a collaborator to edit a template.

List Template Collaborators

Return all collaborators who can edit one template.

List Templates

Return all templates available to the connected account.

Preview Contract Content Update

Preview the prospective Markdown from exact find-and-replace edits without mutating the contract.

Preview Template Content Update

Preview the prospective Markdown from exact find-and-replace edits without mutating the template.

Remove Template Collaborator

Remove a collaborator's permission to edit a template.

Resend Sign Request

Resend a signature request to one signer.

Send Draft Contract

Send an existing draft to its signers.

Update Contract Content

Apply exact Markdown find-and-replace edits to a contract.

Update Contract Placeholder Fields

Update selected placeholder replacements on an unsigned contract.

Update Contract Signer

Update selected contact, delivery, authentication, or redirect details for a signer without resending the contract.

Update Template

Update a template's title and/or labels without changing its Markdown content.

Update Template Content

Apply exact Markdown find-and-replace edits to a template.

Withdraw Contract

Irreversibly withdraw an active unsigned contract so it can no longer be signed.

FAQ

Frequently asked questions

With a standalone eSignatures MCP server, the agents and LLMs can only access a fixed set of eSignatures tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from eSignatures and many other apps based on the task at hand, all through a single MCP endpoint.

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 eSignatures tools.

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

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 eSignatures data and credentials are handled as safely as possible.

Start with eSignatures.It takes 30 seconds.

Managed auth, hosted MCP servers, and every eSignatures tool your agent needs.Free to start.

Start building