# How to integrate Ignisign MCP with Mastra AI ```json { "title": "How to integrate Ignisign MCP with Mastra AI", "toolkit": "Ignisign", "toolkit_slug": "ignisign", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/ignisign/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/ignisign/framework/mastra-ai.md", "updated_at": "2026-05-12T10:15:40.413Z" } ``` ## Introduction 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. ## Also integrate Ignisign with - [OpenAI Agents SDK](https://composio.dev/toolkits/ignisign/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ignisign/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ignisign/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ignisign/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ignisign/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ignisign/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ignisign/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ignisign/framework/cli) - [Google ADK](https://composio.dev/toolkits/ignisign/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ignisign/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ignisign/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/ignisign/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ignisign/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 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. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `IGNISIGN_API_AUTHENTICATION` | Ignisign API Authentication | Tool to authenticate an application over Ignisign API and retrieve a JWT. Use when obtaining a bearer token before making other API calls. | | `IGNISIGN_CANCEL_SIGNATURE_REQUEST` | Cancel Signature Request | Cancel (close) a signature request to terminate it. This uses the Ignisign /close endpoint which permanently cancels the signature workflow. Use this when you need to abort a signature request that is in DRAFT or IN_PROGRESS status. This operation is idempotent - calling it on an already cancelled request returns success without error. | | `IGNISIGN_CREATE_DOCUMENT` | Initialize Document | Tool to initialize a document for a signature request. Use when linking a new document to an existing signature request after creating that request. | | `IGNISIGN_CREATE_SIGNER` | Create Signer | Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile. | | `IGNISIGN_CREATE_WEBHOOK_ENDPOINT` | Create Webhook Endpoint | Tool to create a new webhook endpoint for an application. Use after obtaining application ID and environment to register for event notifications. | | `IGNISIGN_DELETE_DOCUMENT` | Delete Document | Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete. | | `IGNISIGN_DELETE_SIGNATURE_REQUEST` | Delete Ignisign Signature Request | Permanently deletes a signature request from Ignisign by its ID. This action is irreversible and removes the signature request along with all associated data. The signature request ID can be obtained from the IGNISIGN_INIT_SIGNATURE_REQUEST action or IGNISIGN_GET_SIGNATURE_REQUESTS action. | | `IGNISIGN_DELETE_SIGNER` | Delete Signer | Tool to revoke/delete a signer from an Ignisign application environment. This action permanently revokes the signer's access and is idempotent (can be called multiple times on the same signer). Use when you need to remove a signer after confirming their signer ID. | | `IGNISIGN_DELETE_WEBHOOK_ENDPOINT` | Delete Webhook Endpoint | Delete a webhook endpoint by its ID. After deletion, returns the list of remaining webhook endpoints configured for the application environment. Use this tool when you need to remove a webhook that is no longer needed or to clean up unused webhooks. The webhook ID can be obtained from the create webhook or list webhooks endpoints. | | `IGNISIGN_GET_APPLICATION_CONTEXT` | Get application context | Tool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app. | | `IGNISIGN_GET_DOCUMENT_INFORMATION` | Get Document Information | Tool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID. | | `IGNISIGN_GET_MISSING_SIGNER_INPUTS` | Get Missing Signer Inputs | Tool to determine missing inputs needed for a signer in a specific signature profile. Use after selecting a signature profile and signer to identify required fields. | | `IGNISIGN_GET_SIGNATURE_REQUEST_DETAILS` | Get Signature Request Details | Tool to retrieve detailed information for a specific signature request. Use after creating or listing a signature request to inspect its details. | | `IGNISIGN_GET_SIGNATURE_REQUEST_DOCUMENT` | Get Signature Request Document | Tool to retrieve the document associated with a specific signature request. The action downloads the original file of a document. Provide `documentId` to select a specific document or omit to use the first available document of the request. | | `IGNISIGN_GET_SIGNATURE_REQUESTS` | Get Signature Requests | Retrieves a paginated list of signature requests for a specific Ignisign application and environment. Use this to list all signature requests (drafts, in-progress, completed, cancelled) in an application. Each signature request can have associated documents and signers. Returns pagination metadata to iterate through large result sets. Note: The app_env parameter must match your API key's environment scope. | | `IGNISIGN_GET_SIGNED_DOCUMENT` | Get Signed Document | Tool to download the signed document (signature proof) for a signature request. The action will: 1) Resolve the first documentId from the signature request details. 2) Try v4: GET /documents/{documentId}/signatures/PDF_WITH_SIGNATURES 3) Fallback v3: GET /v3/documents/{documentId}/signature-proof 4) Final fallback: GET /documents/{documentId}/file (original file) | | `IGNISIGN_GET_SIGNER_INPUT_CONSTRAINTS` | Get Signer Input Constraints | Tool to get signer input constraints. Use when you need to know which fields are required from signers for a given signer profile. | | `IGNISIGN_GET_SIGNER_INPUTS` | Get Signer Inputs | Retrieves the inputs provided by a specific signer for a signature request. Returns field values the signer has submitted (e.g., firstName, lastName, email). Use this after a signer has been added to a signature request to fetch their profile information. The signer must be associated with the specified signature request. | | `IGNISIGN_GET_SIGNER_PROFILE` | Get Signer Profile | Retrieve detailed information about a specific signer profile by its ID. Use this to get profile settings including integration mode, authentication methods, and associated signers. First use 'Get Signer Profiles' to list available profile IDs. | | `IGNISIGN_GET_SIGNER_PROFILES` | Get Signer Profiles | Retrieve all signer profiles for a specific Ignisign application environment. Use this tool to list all configured signer profiles that define how signers interact with signature requests. Each profile specifies integration mode (BY_SIDE, EMBEDDED, or MACHINE_TO_MACHINE), authentication methods, and other settings. Returns profile IDs which can be used when creating signers or signature requests. | | `IGNISIGN_GET_WEBHOOKS` | Get Webhooks | Retrieves all webhook endpoints configured for a specific Ignisign application environment. Returns the list of webhooks including their URLs, descriptions, and creation timestamps. Use this to audit existing webhook integrations or verify webhook configurations. | | `IGNISIGN_INIT_SIGNATURE_REQUEST` | Initialize Ignisign Signature Request | Initialize a new signature request in Ignisign. This is the first step in creating a signature workflow. After initialization, you can add documents (IGNISIGN_CREATE_DOCUMENT), assign signers (IGNISIGN_CREATE_SIGNER), and publish the request (IGNISIGN_PUBLISH_SIGNATURE_REQUEST) to start the signing process. | | `IGNISIGN_LIST_DOCUMENTS` | List Documents | Tool to retrieve documents linked to a signature request. The action works by calling the signature request context endpoint and extracting its documentIds, then fetching each document detail. | | `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_DATA_JSON` | Provide Document Content Data JSON | Provides JSON content to an existing document in Ignisign. Use this action after creating a document with IGNISIGN_CREATE_DOCUMENT to attach structured JSON data that will be associated with a signature request. The JSON content is stored and can be used for document generation or data binding in signature workflows. | | `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_FILE` | Provide Document Content File | Tool to provide file content for a document. Use after creating a document to attach its file content. | | `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_PRIVATE_FILE` | Provide Document Content Private File | Provides private document content by submitting its SHA-256 hash to IgniSign. Use this after creating a document with IGNISIGN_CREATE_DOCUMENT when the document content should remain private (not uploaded). The hash proves document integrity without exposing its contents. The document status will change to 'PROVIDED' upon success. | | `IGNISIGN_PUBLISH_SIGNATURE_REQUEST` | Publish Signature Request | Tool to publish a draft signature request. Use after adding all documents and signer details to the draft. | | `IGNISIGN_SEARCH_SIGNERS` | Search Signers | Tool to search for signers within an application environment with pagination support. Use after obtaining application ID and environment. Requires a non-empty filter string to search by name, email, or external ID. Use '*' to match all signers. Supports page and pageSize parameters to paginate through large result sets. | | `IGNISIGN_UPDATE_DOCUMENT_INFORMATION` | Update Document Information | Tool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation. | | `IGNISIGN_UPDATE_SIGNATURE_REQUEST` | Update Signature Request | Tool to partially update a signature request in DRAFT state. Use when you need to modify draft request metadata before sending. | | `IGNISIGN_UPDATE_SIGNER` | Update Signer | Updates an existing signer's profile assignment. Use this to change which signer profile a signer is associated with. The signer must already exist in the application environment. Requires: app_id (from Get Application Context), signer_id (from Create Signer or Search Signers), and signer_profile_id (from Get Signer Profiles). | | `IGNISIGN_UPDATE_WEBHOOK_ENDPOINT` | Update Webhook Endpoint | Tool to update an existing webhook endpoint. Use when you have a webhook ID and want to modify its destination URL or description. Example: Update the URL of webhook `68e7adc882353ea4e072bdbe` to `https://example.com/webhook`. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Ignisign MCP server is an implementation of the Model Context Protocol that connects your AI agent to Ignisign. It provides structured and secure access so your agent can perform Ignisign 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 Ignisign 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 Ignisign 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 ```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); ``` ### 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 Ignisign 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: "ignisign-mastra-agent", instructions: "You are an AI agent with Ignisign 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 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 ```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); }); ``` ## 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: ["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 ## How to build Ignisign MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/ignisign/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ignisign/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ignisign/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ignisign/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ignisign/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ignisign/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ignisign/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/ignisign/framework/cli) - [Google ADK](https://composio.dev/toolkits/ignisign/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ignisign/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ignisign/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/ignisign/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ignisign/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 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 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 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. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)