How to integrate eSignatures MCP with Mastra AI

This guide walks you through connecting eSignatures to Mastra AI using the Composio tool router. By the end, you'll have a working eSignatures agent that can draft contracts, send contracts for signing, add signers, manage templates, and check contract details through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a eSignatures account through Composio's eSignatures 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

eSignatures

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

Managed auth

Connect eSignatures 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 eSignatures account through Composio's eSignatures MCP server.

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

Also integrate eSignatures 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 eSignatures tools
Connect Mastra's MCP client to the Composio generated MCP URL
Fetch eSignatures 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 eSignatures 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 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.

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

typescript

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

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

What's happening:

create spins up a short-lived MCP HTTP endpoint for this user
The toolkits array contains "esignatures" for eSignatures 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 eSignatures toolkit

Create the Mastra agent

typescript

const agent = new Agent({
    name: "esignatures-mastra-agent",
    instructions: "You are an AI agent with eSignatures 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: {
        esignatures: 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 eSignatures 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 eSignatures 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: ["esignatures"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "esignatures-mastra-agent",
    instructions: "You are an AI agent with eSignatures 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: { esignatures: 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 eSignatures 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 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.

FRAMEWORKS

How to build eSignatures MCP Agent with another framework

OpenAI Agents SDK

Use eSignatures MCP with OpenAI Agents SDK

Claude Agent SDK

Use eSignatures MCP with Claude Agent SDK

Claude Code

Use eSignatures MCP with Claude Code

Claude Cowork

Use eSignatures MCP with Claude Cowork

Codex

Use eSignatures MCP with Codex

OpenClaw

Use eSignatures MCP with OpenClaw

Hermes

Use eSignatures MCP with Hermes

CLI

Use eSignatures MCP with CLI

Google ADK

Use eSignatures MCP with Google ADK

LangChain

Use eSignatures MCP with LangChain

Vercel AI SDK

Use eSignatures MCP with Vercel AI SDK

LlamaIndex

Use eSignatures MCP with LlamaIndex

CrewAI

Use eSignatures MCP with CrewAI

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Boloforms

Api Key

BoloForms is an eSignature platform built for small businesses, offering unlimited signatures, templates, and forms. It simplifies digital document signing and team collaboration at a predictable, fixed price.

Box

Oauth2

Box is a cloud content management and file sharing platform for businesses. It helps teams securely store, organize, and collaborate on files from anywhere.

Carbone

Api Key

Carbone is a blazing-fast report generator that turns JSON data into PDFs, Word docs, spreadsheets, and more using flexible templates. It lets you automate document creation at scale with minimal code.

Castingwords

Api Key

CastingWords is a transcription service specializing in human-powered, accurate transcripts via a simple API. Get seamless audio-to-text conversion for interviews, meetings, podcasts, and more.

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

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 eSignatures MCP with Mastra AI

Connect eSignatures without auth hassles

Introduction

Also integrate eSignatures with

TL;DR

What is Mastra AI?

What is the eSignatures 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 eSignatures

Configure Mastra MCP client and fetch tools

Create the Mastra agent

Set up interactive chat interface

Complete Code

Conclusion

Supported Tools

How to build eSignatures 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

Boloforms

Box

Carbone

Castingwords

Frequently asked questions

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

Can I use Tool Router MCP with Mastra AI?+

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

How safe is my data with Composio Tool Router?+

Start with eSignatures.It takes 30 seconds.

Teams ship real agents on Composio