How to integrate Ignisign MCP with Mastra AI

This guide walks you through connecting Ignisign to Mastra AI using the Composio tool router. By the end, you'll have a working Ignisign agent that can start a new signature request for a contract, add a new signer to this application, delete a completed document by its id through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Ignisign account through Composio's Ignisign MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

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

Managed auth

Connect Ignisign without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

This guide will help you understand how to give your Mastra AI agent real control over a Ignisign account through Composio's Ignisign MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Ignisign with

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Set up your environment so Mastra, OpenAI, and Composio work together
Create a Tool Router session in Composio that exposes Ignisign tools
Connect Mastra's MCP client to the Composio generated MCP URL
Fetch Ignisign tool definitions and attach them as a toolset
Build a Mastra agent that can reason, call tools, and return structured results
Run an interactive CLI where you can chat with your Ignisign agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

MCP Client: Built-in support for Model Context Protocol servers
Toolsets: Organize tools into logical groups
Step Callbacks: Monitor and debug agent execution
OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS

Prerequisites

Before starting, make sure you have:

Node.js 18 or higher
A Composio account with an active API key
An OpenAI API key
Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key.
You need credits or a connected billing setup to use the models.
Store the key somewhere safe.

Composio API Key

Log in to the Composio dashboard.
Go to Settings and copy your API key.
This key lets your Mastra agent talk to Composio and reach Ignisign through MCP.

Install dependencies

bash

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

Install the required packages.

What's happening:

@composio/core is the Composio SDK for creating MCP sessions
@mastra/core provides the Agent class
@mastra/mcp is Mastra's MCP client
@ai-sdk/openai is the model wrapper for OpenAI
dotenv loads environment variables from .env

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates your requests to Composio
COMPOSIO_USER_ID tells Composio which user this session belongs to
OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});

What's happening:

dotenv/config auto loads your .env so process.env.* is available
openai gives you a Mastra compatible model wrapper
Agent is the Mastra agent that will call tools and produce answers
MCPClient connects Mastra to your Composio MCP server
Composio is used to create a Tool Router session

Create a Tool Router session for Ignisign

typescript

async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["ignisign"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Ignisign MCP URL:", composioMCPUrl);

What's happening:

create spins up a short-lived MCP HTTP endpoint for this user
The toolkits array contains "ignisign" for Ignisign access
session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript

const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);

What's happening:

MCPClient takes an id for this client and a list of MCP servers
The headers property includes the x-api-key for authentication
getTools fetches the tool definitions exposed by the Ignisign toolkit

Create the Mastra agent

typescript

const agent = new Agent({
    name: "ignisign-mastra-agent",
    instructions: "You are an AI agent with Ignisign tools via Composio.",
    model: "openai/gpt-5",
  });

What's happening:

Agent is the core Mastra agent
name is just an identifier for logging and debugging
instructions guide the agent to use tools instead of only answering in natural language
model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript

let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

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

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        ignisign: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

What's happening:

messages keeps the full conversation history in Mastra's expected format
agent.generate runs the agent with conversation history and Ignisign toolsets
maxSteps limits how many tool calls the agent can take in a single run
onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Ignisign and Mastra AI:

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["ignisign"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      ignisign: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "ignisign-mastra-agent",
    instructions: "You are an AI agent with Ignisign tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { ignisign: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Ignisign through Composio's Tool Router. You can extend this further by:

Adding other toolkits like Gmail, Slack, or GitHub
Building a web-based chat interface around this agent
Using multiple MCP endpoints to enable cross-app workflows

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.

FRAMEWORKS

How to build Ignisign MCP Agent with another framework

OpenAI Agents SDK

Use Ignisign MCP with OpenAI Agents SDK

Claude Agent SDK

Use Ignisign MCP with Claude Agent SDK

Claude Code

Use Ignisign MCP with Claude Code

Claude Cowork

Use Ignisign MCP with Claude Cowork

Codex

Use Ignisign MCP with Codex

OpenClaw

Use Ignisign MCP with OpenClaw

Hermes

Use Ignisign MCP with Hermes

CLI

Use Ignisign MCP with CLI

Google ADK

Use Ignisign MCP with Google ADK

LangChain

Use Ignisign MCP with LangChain

Vercel AI SDK

Use Ignisign MCP with Vercel AI SDK

LlamaIndex

Use Ignisign MCP with LlamaIndex

CrewAI

Use Ignisign MCP with CrewAI

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.

Affinda

Api Key

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.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Ignisign.It takes 30 seconds.

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

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Ignisign MCP with Mastra AI

Connect Ignisign without auth hassles

Introduction

Also integrate Ignisign with

TL;DR

What is Mastra AI?

What is the Ignisign MCP server, and what's possible with it?

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import libraries and validate environment

Create a Tool Router session for Ignisign

Configure Mastra MCP client and fetch tools

Create the Mastra agent

Set up interactive chat interface

Complete Code

Conclusion

Supported Tools

How to build Ignisign MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

LlamaIndex

CrewAI

Explore Other Toolkits

Google Drive

Google Docs

Google Super

Affinda

Frequently asked questions

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

Can I use Tool Router MCP with Mastra AI?+

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

How safe is my data with Composio Tool Router?+

Start with Ignisign.It takes 30 seconds.

Teams ship real agents on Composio