How to integrate Ignisign MCP with Codex

GET STARTED FOR FREE
Ignisign logo
Codex logo
divider

Introduction

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

Also integrate Ignisign 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 Ignisign 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 connect.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 Ignisign MCP server, and what's possible with it?

The Ignisign MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ignisign account. It provides structured and secure access to your electronic signature workflows, so your agent can perform actions like sending signature requests, managing documents, onboarding signers, and handling signature operations on your behalf.

  • Automated signature request management: Let your agent create, cancel, or delete signature requests, streamlining the entire e-signature process from start to finish.
  • Document initialization and deletion: Have the agent initialize new documents for signing or permanently delete documents when they're no longer needed.
  • Signer onboarding and removal: Effortlessly add new signers to your application environment or remove existing ones as your workflows change.
  • Webhook endpoint management: Allow your agent to create or delete webhook endpoints, enabling real-time notifications and integrations for signature events.
  • Application context retrieval: Fetch global application settings and environment configurations so your agent always works with up-to-date information.

Supported Tools & Triggers

Tools
Ignisign API AuthenticationTool to authenticate an application over Ignisign API and retrieve a JWT.
Cancel Signature RequestTool to cancel a signature request.
Initialize DocumentTool to initialize a document for a signature request.
Create SignerTool to create a new signer.
Create Webhook EndpointTool to create a new webhook endpoint for an application.
Delete DocumentTool to delete a specific document by its ID.
Delete Ignisign Signature RequestTool to delete a signature request.
Delete SignerTool to delete a signer.
Delete Webhook EndpointTool to delete a specific webhook endpoint.
Get application contextTool to retrieve the global context of an application.
Get Document InformationTool to retrieve document metadata by ID.
Get Missing Signer InputsTool to determine missing inputs needed for a signer in a specific signature profile.
Get Signature Request DetailsTool to retrieve detailed information for a specific signature request.
Get Signature Request DocumentTool to retrieve the document associated with a specific signature request.
Get Signature RequestsTool to retrieve a paginated list of signature requests for an application.
Get Signature Request StatusTool to retrieve the current status of a specific signature request.
Get Signed DocumentTool to download the signed document (signature proof) for a signature request.
Get Signer Creation ConstraintsTool to retrieve input constraints required to create a signer for a specific signature profile.
Get Signer Input ConstraintsTool to get signer input constraints.
Get Signer InputsTool to retrieve inputs provided by a signer for a signature request.
Get Signer ProfileTool to retrieve a signer profile.
Get Signer ProfilesTool to retrieve signer profiles.
Get Webhook DetailsTool to retrieve details of a specific webhook endpoint.
Get WebhooksTool to list all webhook endpoints configured for an application environment.
Close Ignisign Signature RequestTool to close an active signature request.
Update SignerTool to update details of an existing signer.
Initialize Ignisign Signature RequestTool to initialize a new signature request.
List DocumentsTool to retrieve documents linked to a signature request.
Provide Document Content Data JSONTool to provide JSON content for a document.
Provide Document Content FileTool to provide file content for a document.
Provide Document Content Private FileTool to provide private content for a document via its SHA-256 hash.
Publish Signature RequestTool to publish a draft signature request.
Search SignersTool to search for signers within an application.
Update Document InformationTool to update document metadata.
Update Signature RequestTool to partially update a signature request in DRAFT state.
Update Webhook EndpointTool to update an existing webhook endpoint.

Conclusion

You've successfully integrated Ignisign with Codex using Composio's MCP server. Now you can interact with Ignisign 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 Ignisign 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 Ignisign operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Ignisign MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Ignisign MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Ignisign MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Ignisign MCP with Claude Code

OpenClaw logo

OpenClaw

Use Ignisign MCP with OpenClaw

CLI logo

CLI

Use Ignisign MCP with CLI

Google ADK logo

Google ADK

Use Ignisign MCP with Google ADK

LangChain logo

LangChain

Use Ignisign MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Ignisign MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Ignisign MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Ignisign MCP with LlamaIndex

CrewAI logo

CrewAI

Use Ignisign MCP with CrewAI

FAQ

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

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

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

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

Book a call↗Get started for free