# How to integrate LLMWhisperer MCP with Mastra AI ```json { "title": "How to integrate LLMWhisperer MCP with Mastra AI", "toolkit": "LLMWhisperer", "toolkit_slug": "llmwhisperer", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/llmwhisperer/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/llmwhisperer/framework/mastra-ai.md", "updated_at": "2026-03-29T06:40:48.248Z" } ``` ## Introduction This guide walks you through connecting LLMWhisperer to Mastra AI using the Composio tool router. By the end, you'll have a working LLMWhisperer agent that can summarize main points from uploaded contract, extract key dates from legal document, classify sections of this technical report through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a LLMWhisperer account through Composio's LLMWhisperer MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate LLMWhisperer with - [OpenAI Agents SDK](https://composio.dev/toolkits/llmwhisperer/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/llmwhisperer/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/llmwhisperer/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/llmwhisperer/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/llmwhisperer/framework/codex) - [OpenClaw](https://composio.dev/toolkits/llmwhisperer/framework/openclaw) - [Hermes](https://composio.dev/toolkits/llmwhisperer/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/llmwhisperer/framework/cli) - [Google ADK](https://composio.dev/toolkits/llmwhisperer/framework/google-adk) - [LangChain](https://composio.dev/toolkits/llmwhisperer/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/llmwhisperer/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/llmwhisperer/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/llmwhisperer/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 LLMWhisperer tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch LLMWhisperer 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 LLMWhisperer 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 LLMWhisperer MCP server, and what's possible with it? The LLMWhisperer MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your LLMWhisperer account. It provides structured and secure access so your agent can perform LLMWhisperer operations on your behalf. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `LLMWHISPERER_USAGE_GET_INFO` | Get Usage Information | Tool to check usage metrics of your LLMWhisperer account. Use when you need to monitor API consumption, verify quotas, or check remaining page limits. | | `LLMWHISPERER_USAGE_GET_STATS` | Get Usage Statistics | Tool to retrieve usage statistics for your LLMWhisperer account based on a specific tag. Use when you need to check consumption metrics for a given tag and optional date range. Returns usage data for the preceding 30 days when date parameters are omitted. | | `LLMWHISPERER_WEBHOOK_DELETE` | Delete Webhook | Tool to delete a registered webhook from LLMWhisperer system. Use when you need to remove a webhook that is no longer needed. | | `LLMWHISPERER_WEBHOOK_GET_DETAILS` | Get Webhook Details | Tool to retrieve registered webhook details for LLMWhisperer. Use when you need to get the configuration of a specific webhook including its URL and authentication token. | | `LLMWHISPERER_REGISTER_WEBHOOK` | Register Webhook | Tool to register a new webhook endpoint for LLMWhisperer async notifications. Use when you need to set up a callback URL to receive processing results. During registration, a test payload is sent to verify the webhook endpoint is functioning and returns HTTP 200. | | `LLMWHISPERER_UPDATE_WEBHOOK_CONFIGURATION` | Update Webhook Configuration | Tool to update an existing webhook configuration for document conversion callbacks. Use when you need to modify the callback URL, authentication token, or webhook identifier. The system validates the webhook by sending a test payload and requires a 200 status response. | | `LLMWHISPERER_CHECK_WHISPER_STATUS` | Check Whisper Status | Tool to check the status of a text extraction process in LLMWhisperer. Use when the conversion is done in async mode to poll for completion status. | | `LLMWHISPERER_CONVERT_DOCUMENT_TO_TEXT` | Convert Document to Text | Tool to convert PDFs and scanned documents into LLM-optimized text format asynchronously. Use when you need to extract text from documents for LLM processing. After submission, use the returned whisper_hash to poll status and retrieve converted text. Either document_url (with url_in_post=true) or document_content must be provided. | | `LLMWHISPERER_GET_WHISPER_DETAIL` | Get Whisper Detail | Tool to retrieve comprehensive details about ongoing or completed text extraction process. Use when you need to monitor the status and progress metrics of a text extraction job. | | `LLMWHISPERER_RETRIEVE_WHISPER_TEXT` | Retrieve Whisper Text | Tool to retrieve extracted text from asynchronous whisper processing. Use when the conversion process was initiated in async mode and you need to retrieve the results using the whisper_hash identifier. Note that retrieval is single-use for security - once retrieved, the same whisper_hash cannot be used again. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The LLMWhisperer MCP server is an implementation of the Model Context Protocol that connects your AI agent to LLMWhisperer. It provides structured and secure access so your agent can perform LLMWhisperer 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 LLMWhisperer 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 LLMWhisperer What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "llmwhisperer" for LLMWhisperer 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: ["llmwhisperer"], }, ); const composioMCPUrl = session.mcp.url; console.log("LLMWhisperer 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 LLMWhisperer 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: "llmwhisperer-mastra-agent", instructions: "You are an AI agent with LLMWhisperer 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 LLMWhisperer 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: { llmwhisperer: 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: ["llmwhisperer"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { llmwhisperer: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "llmwhisperer-mastra-agent", instructions: "You are an AI agent with LLMWhisperer 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: { llmwhisperer: 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 LLMWhisperer 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 LLMWhisperer MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/llmwhisperer/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/llmwhisperer/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/llmwhisperer/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/llmwhisperer/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/llmwhisperer/framework/codex) - [OpenClaw](https://composio.dev/toolkits/llmwhisperer/framework/openclaw) - [Hermes](https://composio.dev/toolkits/llmwhisperer/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/llmwhisperer/framework/cli) - [Google ADK](https://composio.dev/toolkits/llmwhisperer/framework/google-adk) - [LangChain](https://composio.dev/toolkits/llmwhisperer/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/llmwhisperer/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/llmwhisperer/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/llmwhisperer/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. - [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed. - [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. - [Composio search](https://composio.dev/toolkits/composio_search) - Composio search is a unified web search toolkit spanning travel, e-commerce, news, financial markets, images, and more. It lets you and your apps tap into up-to-date web data from a single, easy-to-integrate service. - [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. - [Perplexityai](https://composio.dev/toolkits/perplexityai) - Perplexityai delivers natural, conversational AI models for generating human-like text. Instantly get context-aware, high-quality responses for chat, search, or complex workflows. - [Browser tool](https://composio.dev/toolkits/browser_tool) - Browser tool is a virtual browser integration that lets AI agents interact with the web programmatically. It enables automated browsing, scraping, and action-taking from any AI workflow. - [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. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and LLMWhisperer MCP? With a standalone LLMWhisperer MCP server, the agents and LLMs can only access a fixed set of LLMWhisperer tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from LLMWhisperer 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 LLMWhisperer tools. ### Can I manage the permissions and scopes for LLMWhisperer while using Tool Router? Yes, absolutely. You can configure which LLMWhisperer 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 LLMWhisperer data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)