# How to integrate Docsautomator MCP with Mastra AI ```json { "title": "How to integrate Docsautomator MCP with Mastra AI", "toolkit": "Docsautomator", "toolkit_slug": "docsautomator", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/docsautomator/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/docsautomator/framework/mastra-ai.md", "updated_at": "2026-03-29T06:30:49.122Z" } ``` ## Introduction This guide walks you through connecting Docsautomator to Mastra AI using the Composio tool router. By the end, you'll have a working Docsautomator agent that can generate an invoice from the 'invoice' template, create onboarding document for new employee, list all docsautomator templates available to me through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Docsautomator account through Composio's Docsautomator MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Docsautomator with - [OpenAI Agents SDK](https://composio.dev/toolkits/docsautomator/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/docsautomator/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/docsautomator/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/docsautomator/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/docsautomator/framework/codex) - [OpenClaw](https://composio.dev/toolkits/docsautomator/framework/openclaw) - [Hermes](https://composio.dev/toolkits/docsautomator/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/docsautomator/framework/cli) - [Google ADK](https://composio.dev/toolkits/docsautomator/framework/google-adk) - [LangChain](https://composio.dev/toolkits/docsautomator/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/docsautomator/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/docsautomator/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/docsautomator/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 Docsautomator tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch Docsautomator 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 Docsautomator 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 Docsautomator MCP server, and what's possible with it? The Docsautomator MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Docsautomator account. It provides structured and secure access so your agent can perform Docsautomator operations on your behalf. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `DOCSAUTOMATOR_CREATE_AUTOMATION` | Create Automation | Tool to create a new DocsAutomator automation with specified data source and optional Google Doc template. Use when you need to set up a new document automation workflow. PDF templates must be uploaded through the DocsAutomator app interface. | | `DOCSAUTOMATOR_DELETE_AUTOMATION` | Delete Automation | Tool to permanently delete an automation and all associated data. Use when you need to remove an automation that is no longer needed. This action cannot be undone. | | `DOCSAUTOMATOR_DUPLICATE_AUTOMATION` | Duplicate Automation | Tool to create a copy of an existing automation with ' COPY' appended to the title. Use when you need to duplicate an existing automation without recreating it from scratch. | | `DOCSAUTOMATOR_GET_AUTOMATION` | Get Automation Details | Tool to retrieve details of a specific automation by its ID. Use when you need to fetch configuration, data source settings, and template information for an automation. | | `DOCSAUTOMATOR_GET_QUEUE_STATISTICS` | Get Queue Statistics | Tool to retrieve current document generation queue statistics for your workspace. Use when monitoring queue health or checking processing capacity. | | `DOCSAUTOMATOR_LIST_AUTOMATIONS` | List Automations | Tool to retrieve all automations in your workspace with their basic details. Use when you need to view, list, or enumerate existing automations. | | `DOCSAUTOMATOR_LIST_SIGNING_SESSIONS` | List Signing Sessions | Tool to retrieve signing sessions with optional filtering by status or signer email. Returns paginated results. Use when you need to list or search for signing sessions in DocsAutomator. | | `DOCSAUTOMATOR_SEND_TEST_EMAIL` | Send Test Email | Tool to send a test email with a sample PDF attachment to verify email configuration. Use when you need to test email delivery for a specific automation. Rate limited to 25 emails per hour per automation. | | `DOCSAUTOMATOR_UPDATE_AUTOMATION` | Update Automation | Tool to update an existing automation's settings in DocsAutomator. Only the fields included in the request are updated. Use when you need to modify automation properties like title, template link, locale settings, or activation status. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Docsautomator MCP server is an implementation of the Model Context Protocol that connects your AI agent to Docsautomator. It provides structured and secure access so your agent can perform Docsautomator 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 Docsautomator 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 Docsautomator What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "docsautomator" for Docsautomator 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: ["docsautomator"], }, ); const composioMCPUrl = session.mcp.url; console.log("Docsautomator 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 Docsautomator 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: "docsautomator-mastra-agent", instructions: "You are an AI agent with Docsautomator 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 Docsautomator 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: { docsautomator: 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: ["docsautomator"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { docsautomator: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "docsautomator-mastra-agent", instructions: "You are an AI agent with Docsautomator 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: { docsautomator: 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 Docsautomator 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 Docsautomator MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/docsautomator/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/docsautomator/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/docsautomator/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/docsautomator/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/docsautomator/framework/codex) - [OpenClaw](https://composio.dev/toolkits/docsautomator/framework/openclaw) - [Hermes](https://composio.dev/toolkits/docsautomator/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/docsautomator/framework/cli) - [Google ADK](https://composio.dev/toolkits/docsautomator/framework/google-adk) - [LangChain](https://composio.dev/toolkits/docsautomator/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/docsautomator/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/docsautomator/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/docsautomator/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 Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly. - [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place. - [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations. - [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. - [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals. - [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem. - [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity. - [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently. - [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place. - [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [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. - [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place. - [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. - [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Docsautomator MCP? With a standalone Docsautomator MCP server, the agents and LLMs can only access a fixed set of Docsautomator tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Docsautomator 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 Docsautomator tools. ### Can I manage the permissions and scopes for Docsautomator while using Tool Router? Yes, absolutely. You can configure which Docsautomator 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 Docsautomator data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)