Ignisign MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Ignisign MCP or direct API to sign documents, send signature requests, manage templates, and track signing status through natural language.

Get started for free Get a demo

Ignisign

Api Key

Ignisign is an electronic signature platform for secure online document signing and management. Streamline agreements and digital paperwork with advanced workflow tools.

32 Tools

Try Ignisign now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND

Ignisign

Enter ↵

Try asking

TOOLS

Supported Tools

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

Ignisign API Authentication

Tool to authenticate an application over Ignisign API and retrieve a JWT.

Cancel Signature Request

Cancel (close) a signature request to terminate it.

Initialize Document

Tool to initialize a document for a signature request.

Create Signer

Tool to create a new signer.

Create Webhook Endpoint

Tool to create a new webhook endpoint for an application.

Delete Document

Tool to delete a specific document by its ID.

Delete Ignisign Signature Request

Permanently deletes a signature request from Ignisign by its ID.

Delete Signer

Tool to revoke/delete a signer from an Ignisign application environment.

Delete Webhook Endpoint

Delete a webhook endpoint by its ID.

Get application context

Tool to retrieve the global context of an application.

Get Document Information

Tool to retrieve document metadata by ID.

Get Missing Signer Inputs

Tool to determine missing inputs needed for a signer in a specific signature profile.

Get Signature Request Details

Tool to retrieve detailed information for a specific signature request.

Get Signature Request Document

Tool to retrieve the document associated with a specific signature request.

Get Signature Requests

Retrieves a paginated list of signature requests for a specific Ignisign application and environment.

Get Signed Document

Tool to download the signed document (signature proof) for a signature request.

Get Signer Input Constraints

Tool to get signer input constraints.

Get Signer Inputs

Retrieves the inputs provided by a specific signer for a signature request.

Get Signer Profile

Retrieve detailed information about a specific signer profile by its ID.

Get Signer Profiles

Retrieve all signer profiles for a specific Ignisign application environment.

Get Webhooks

Retrieves all webhook endpoints configured for a specific Ignisign application environment.

Initialize Ignisign Signature Request

Initialize a new signature request in Ignisign.

List Documents

Tool to retrieve documents linked to a signature request.

Provide Document Content Data JSON

Provides JSON content to an existing document in Ignisign.

Provide Document Content File

Tool to provide file content for a document.

Provide Document Content Private File

Provides private document content by submitting its SHA-256 hash to IgniSign.

Publish Signature Request

Tool to publish a draft signature request.

Search Signers

Tool to search for signers within an application environment with pagination support.

Update Document Information

Tool to update document metadata.

Update Signature Request

Tool to partially update a signature request in DRAFT state.

Update Signer

Updates an existing signer's profile assignment.

Update Webhook Endpoint

Tool to update an existing webhook endpoint.

SETUP GUIDE

Connect Ignisign MCP Tool with your Agent

Install Composio

typescript

npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai

Install the Composio SDK and your agent framework

Create a session with MCP enabled

typescript

import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["ignisign"],
  mcp: true,
});

Create a session scoped to Ignisign and read its MCP URL and headers

Connect your agent to the MCP server

typescript

import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "Send a contract for signature to a new client",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();

Pass the session's MCP URL and headers to your agent and run a Ignisign request

SETUP GUIDE

Connect Ignisign API Tool with your Agent

Install Composio

typescript

npm install @composio/core @composio/openai openai

Install the Composio SDK, the OpenAI provider, and the OpenAI SDK

Create a Composio session

typescript

import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["ignisign"] });
const tools = await session.tools();

Initialize Composio with the OpenAI Responses provider and create a session scoped to Ignisign

Run Ignisign tools with your agent

typescript

let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "Send a contract for signature to a new client" }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);

Send a request, execute the Ignisign tool calls through the session, and print the final answer

Why Use Composio?

AI Native Ignisign Integration

Supports both Ignisign MCP and direct API based integrations
Structured, LLM-friendly schemas for reliable tool execution
Rich coverage for reading, writing, and querying your Ignisign data

Managed Auth

Built-in API key management with secure token storage
Central place to manage, scope, and revoke Ignisign access
Per user and per environment credentials instead of hard-coded keys

Agent Optimized Design

Tools are tuned using real error and success rates to improve reliability over time
Comprehensive execution logs so you always know what ran, when, and on whose behalf

Enterprise Grade Security

Fine-grained RBAC so you control which agents and users can access Ignisign
Scoped, least privilege access to Ignisign resources
Full audit trail of agent actions to support review and compliance

FRAMEWORKS

Use Ignisign with any AI Agent Framework

Choose a Framework you want to connect Ignisign with

Claude Code

Use Ignisign MCP with Claude Code

Claude Cowork

Use Ignisign MCP with Claude Cowork

OpenAI Agents SDK

Use Ignisign MCP with OpenAI Agents SDK

Claude Agents SDK

Use Ignisign MCP with Claude Agents SDK

Codex

Use Ignisign MCP with Codex

OpenClaw

Use Ignisign MCP with OpenClaw

Hermes

Use Ignisign MCP with Hermes

Atomic Agent

Use Ignisign MCP with Atomic Agent

Google ADK

Use Ignisign MCP with Google ADK

Langchain

Use Ignisign MCP with Langchain

AI SDK

Use Ignisign MCP with AI SDK

Mastra AI

Use Ignisign MCP with Mastra AI

LlamaIndex

Use Ignisign MCP with LlamaIndex

CrewAI

Use Ignisign MCP with CrewAI

Pydantic AI

Use Ignisign MCP with Pydantic AI

Autogen

Use Ignisign MCP with Autogen

Rolling this out across your team?

Give your team centralized access control across every framework with Composio’s MCP Gateway.

EXPLORE MCP GATEWAY

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Google Drive

Oauth2

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

Oauth2

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

Oauth2Api Key

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.

ActiveMerge

Api Key

ActiveMerge is a document automation platform for generating documents, images, merged files, and e-signature workflows. It helps teams turn templates and stored files into finished, shareable documents faster.

FAQ

Frequently asked questions

Yes, Ignisign requires you to configure your own API key credentials. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your Ignisign connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your Ignisign account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the Ignisign actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside Ignisign at any time.

When you connect a Ignisign account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in Ignisign as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside Ignisign. If Ignisign lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside Ignisign at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each Ignisign connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment Ignisign rejects the old key. Create a new key in Ignisign and reconnect the account from the Composio dashboard or by asking your agent to reconnect Ignisign. Nothing else changes.

Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal Ignisign use. Paid plans add higher limits and team features. Your Ignisign plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple Ignisign accounts).

With Composio, you connect Ignisign once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

Start with Ignisign.It takes 30 seconds.

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

Start building

Ignisign MCP server for AI agents and assistants

Try Ignisign now

Supported Tools

Connect Ignisign MCP Tool with your Agent

Install Composio

Create a session with MCP enabled

Connect your agent to the MCP server

Connect Ignisign API Tool with your Agent

Install Composio

Create a Composio session

Run Ignisign tools with your agent

Why Use Composio?

AI Native Ignisign Integration

Managed Auth

Agent Optimized Design

Enterprise Grade Security

Use Ignisign with any AI Agent Framework

Claude Code

Claude Cowork

OpenAI Agents SDK

Claude Agents SDK

Codex

OpenClaw

Hermes

Atomic Agent

Google ADK

Langchain

AI SDK

Mastra AI

LlamaIndex

CrewAI

Pydantic AI

Autogen

Rolling this out across your team?

Explore Other Toolkits

Google Drive

Google Docs

Google Super

ActiveMerge

Frequently asked questions

Do I need my own developer credentials to use Ignisign with Composio?+

Can I use multiple toolkits together?+

Is Composio secure with my Ignisign account?+

What if the API changes?+

Where do I get a Ignisign API key, and who can see it?+

Does the agent act as me inside Ignisign?+

Which Ignisign permissions does the agent get?+

Can I use multiple Ignisign accounts with Claude and ChatGPT?+

What happens if I rotate or revoke my Ignisign API key?+

Does using Ignisign through Composio cost extra?+

How is Composio different from the Ignisign connectors already built into Claude and ChatGPT?+

Start with Ignisign.It takes 30 seconds.