# How to integrate Esignatures io MCP with Mastra AI ```json { "title": "How to integrate Esignatures io MCP with Mastra AI", "toolkit": "Esignatures io", "toolkit_slug": "esignatures_io", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/esignatures_io/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/esignatures_io/framework/mastra-ai.md", "updated_at": "2026-05-12T10:10:34.742Z" } ``` ## Introduction This guide walks you through connecting Esignatures io to Mastra AI using the Composio tool router. By the end, you'll have a working Esignatures io agent that can send a contract to a new client for signature, list all available contract templates, withdraw a contract that hasn't been signed through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Esignatures io account through Composio's Esignatures io MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Esignatures io with - [OpenAI Agents SDK](https://composio.dev/toolkits/esignatures_io/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/esignatures_io/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/esignatures_io/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/esignatures_io/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/esignatures_io/framework/codex) - [OpenClaw](https://composio.dev/toolkits/esignatures_io/framework/openclaw) - [Hermes](https://composio.dev/toolkits/esignatures_io/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/esignatures_io/framework/cli) - [Google ADK](https://composio.dev/toolkits/esignatures_io/framework/google-adk) - [LangChain](https://composio.dev/toolkits/esignatures_io/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/esignatures_io/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/esignatures_io/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/esignatures_io/framework/crew-ai) ## 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 io tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch Esignatures io 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 io 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 io MCP server, and what's possible with it? The Esignatures io 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 io account. It provides structured and secure access to your contract management tools, so your agent can create contracts, manage templates, handle signer profiles, and control contract workflows seamlessly on your behalf. - Automated contract creation and sending: Instantly generate and send new contracts for signature using pre-built templates and custom signer details. - Template management and organization: Allow your agent to create, retrieve, list, and delete contract templates for easy document standardization and reuse. - Signer profile creation: Effortlessly add new signers to your account, making it simple to initiate or update signature requests as needed. - Contract withdrawal and workflow control: Instantly withdraw contracts that should no longer be signed, preventing further action on outdated or incorrect documents. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `ESIGNATURES_IO_ADD_TEMPLATE_COLLABORATOR` | Add Template Collaborator | Tool to grant editing access to a template with optional email invitation. Use when you need to add a collaborator who can edit the template. | | `ESIGNATURES_IO_COPY_TEMPLATE` | Copy Template | Tool to duplicate an existing template with optional customization. Use when you need to create a new template based on an existing one. | | `ESIGNATURES_IO_CREATE_CONTRACT` | Create Contract | Tool to create a new contract using a specified template and signer details. Use after selecting a template when you need to send a contract for signature. | | `ESIGNATURES_IO_CREATE_SIGNER` | Create Signer | Add a signer to an existing contract/signature request. This action queues the addition of a new signer to a contract that has already been created. The signer will be added asynchronously and will receive their signing invitation via email. Use this when you need to add additional signers to a contract after it has been created, or when you want to add signers incrementally rather than all at once during contract creation. Note: The API returns a queued status, indicating the operation has been accepted for processing. Adding a new signer does not automatically send an email notification unless the contract settings are configured to do so. | | `ESIGNATURES_IO_CREATE_TEMPLATE` | Create Template | Tool to create a new template. Use when you want to register a reusable contract template after defining document elements. | | `ESIGNATURES_IO_DELETE_SIGNER` | Delete Signer | Tool to remove a signer from a contract. Use when you need to revoke a signer's access to sign a contract. | | `ESIGNATURES_IO_DELETE_TEMPLATE` | Delete Template | Tool to delete a specific template by its ID. Use when you need to remove an unused or outdated template after confirming its ID. | | `ESIGNATURES_IO_GENERATE_CONTRACT_PDF_PREVIEW` | Generate Contract PDF Preview | Tool to generate a PDF preview of a contract and receive a webhook notification with a download URL. Use when you need to preview the contract document before or after signing. | | `ESIGNATURES_IO_GET_CONTRACT` | Get Contract | Tool to retrieve details of a specific contract by its ID. Returns contract status, signer information, and values entered by signers. Use when you need to check contract status or download signed PDF. | | `ESIGNATURES_IO_GET_TEMPLATE` | Get Template | Tool to retrieve details of a specific template by its ID. Use when you need to fetch a template’s metadata after selecting its ID. | | `ESIGNATURES_IO_LIST_TEMPLATE_COLLABORATORS` | List Template Collaborators | Tool to retrieve all collaborators with editing access to a template. Returns collaborator IDs, names, emails, and editor URLs. | | `ESIGNATURES_IO_LIST_TEMPLATES` | List Templates | Tool to retrieve a list of all templates. Use when you need to browse available templates before selecting one. | | `ESIGNATURES_IO_REMOVE_TEMPLATE_COLLABORATOR` | Remove Template Collaborator | Tool to revoke a collaborator's template editing permissions. Use when you need to remove access for a specific collaborator from a template. | | `ESIGNATURES_IO_SEND_CONTRACT_TO_SIGNER` | Send Contract to Signer | Tool to send or resend a contract signature request to a specific signer via their configured communication channel. Use when you need to deliver a contract to a signer for their signature. | | `ESIGNATURES_IO_UPDATE_SIGNER` | Update Signer | Tool to update contact details of an existing signer on a contract. Use when you need to change a signer's name, email, or mobile number. Note: The contract is not automatically emailed when the signer's information is updated. | | `ESIGNATURES_IO_UPDATE_TEMPLATE` | Update Template | Tool to update an existing template's content, title, or labels. Use when you need to modify a template's configuration without creating a new one. | | `ESIGNATURES_IO_WITHDRAW_CONTRACT` | Withdraw Contract | Tool to withdraw a contract by its ID. Use when you need to prevent further signing of a contract that hasn't been fully signed. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Esignatures io MCP server is an implementation of the Model Context Protocol that connects your AI agent to Esignatures io. It provides structured and secure access so your agent can perform Esignatures io operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. 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 ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings and copy your API key. - This key lets your Mastra agent talk to Composio and reach Esignatures io through MCP. ### 2. Install dependencies 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 ```bash npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv ``` ### 3. Set up environment variables 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 ```bash COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import libraries and validate environment 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 ```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, }); ``` ### 5. Create a Tool Router session for Esignatures io What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "esignatures_io" for Esignatures io access - session.mcp.url is the MCP URL that Mastra's MCPClient will connect to ```typescript async function main() { const session = await composio.create( composioUserID as string, { toolkits: ["esignatures_io"], }, ); const composioMCPUrl = session.mcp.url; console.log("Esignatures io MCP URL:", composioMCPUrl); ``` ### 6. Configure Mastra MCP client and fetch tools 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 io toolkit ```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); ``` ### 7. Create the Mastra agent 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 ```typescript const agent = new Agent({ name: "esignatures_io-mastra-agent", instructions: "You are an AI agent with Esignatures io tools via Composio.", model: "openai/gpt-5", }); ``` ### 8. Set up interactive chat interface What's happening: - messages keeps the full conversation history in Mastra's expected format - agent.generate runs the agent with conversation history and Esignatures io 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 ```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_io: 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); }); ``` ## Complete Code ```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_io"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { esignatures_io: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "esignatures_io-mastra-agent", instructions: "You are an AI agent with Esignatures io 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_io: 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 io 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 ## How to build Esignatures io MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/esignatures_io/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/esignatures_io/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/esignatures_io/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/esignatures_io/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/esignatures_io/framework/codex) - [OpenClaw](https://composio.dev/toolkits/esignatures_io/framework/openclaw) - [Hermes](https://composio.dev/toolkits/esignatures_io/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/esignatures_io/framework/cli) - [Google ADK](https://composio.dev/toolkits/esignatures_io/framework/google-adk) - [LangChain](https://composio.dev/toolkits/esignatures_io/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/esignatures_io/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/esignatures_io/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/esignatures_io/framework/crew-ai) ## Related Toolkits - [Google Drive](https://composio.dev/toolkits/googledrive) - 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](https://composio.dev/toolkits/googledocs) - 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](https://composio.dev/toolkits/googlesuper) - 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](https://composio.dev/toolkits/affinda) - 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. - [Agility cms](https://composio.dev/toolkits/agility_cms) - Agility CMS is a headless content management system for building and managing digital experiences across platforms. It lets teams update content quickly and deliver omnichannel experiences with ease. - [Algodocs](https://composio.dev/toolkits/algodocs) - Algodocs is an AI-powered platform that automates data extraction from business documents. It delivers fast, secure, and accurate processing without templates or manual training. - [Api2pdf](https://composio.dev/toolkits/api2pdf) - Api2Pdf is a REST API for generating PDFs from HTML, URLs, and documents using powerful engines like wkhtmltopdf and Headless Chrome. It streamlines document conversion and automation for developers and businesses. - [Aryn](https://composio.dev/toolkits/aryn) - Aryn is an AI-powered platform for parsing, extracting, and analyzing data from unstructured documents. Use it to automate document processing and unlock actionable insights from your files. - [Boldsign](https://composio.dev/toolkits/boldsign) - Boldsign is a digital eSignature platform for sending, signing, and tracking documents online. Organizations use it to automate agreements and manage legally binding workflows efficiently. - [Boloforms](https://composio.dev/toolkits/boloforms) - 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](https://composio.dev/toolkits/box) - 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](https://composio.dev/toolkits/carbone) - 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](https://composio.dev/toolkits/castingwords) - 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. - [Cloudconvert](https://composio.dev/toolkits/cloudconvert) - CloudConvert is a powerful file conversion service supporting over 200 file formats. It streamlines converting, compressing, and managing documents, media, and more, all in one place. - [Cloudlayer](https://composio.dev/toolkits/cloudlayer) - Cloudlayer is a document and asset generation service for creating PDFs and images via API or SDKs. It lets you automate high-quality doc creation, saving dev time and reducing manual work. - [Cloudpress](https://composio.dev/toolkits/cloudpress) - Cloudpress is a content export tool for Google Docs and Notion. It automates publishing to your favorite Content Management Systems. - [Contentful graphql](https://composio.dev/toolkits/contentful_graphql) - Contentful graphql is a content delivery API that lets you access Contentful data using GraphQL queries. It gives you efficient, flexible ways to fetch and manage structured content for any digital project. - [Conversion tools](https://composio.dev/toolkits/conversion_tools) - Conversion Tools is an online service for converting documents between formats such as PDF, Word, Excel, XML, and CSV. It lets you automate complex document workflows with just a few clicks. - [Convertapi](https://composio.dev/toolkits/convertapi) - ConvertAPI is a robust file conversion service for documents, images, and spreadsheets. It streamlines programmatic format changes and lets developers automate complex workflows with a single API. - [Craftmypdf](https://composio.dev/toolkits/craftmypdf) - CraftMyPDF is a web-based service for designing and generating PDFs with templates and live data. It streamlines document creation by automating personalized PDFs at scale. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Esignatures io MCP? With a standalone Esignatures io MCP server, the agents and LLMs can only access a fixed set of Esignatures io tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Esignatures io and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Mastra AI? 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 io tools. ### Can I manage the permissions and scopes for Esignatures io while using Tool Router? Yes, absolutely. You can configure which Esignatures io 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 Esignatures io data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)