# How to integrate Remote retrieval MCP with Mastra AI ```json { "title": "How to integrate Remote retrieval MCP with Mastra AI", "toolkit": "Remote retrieval", "toolkit_slug": "remote_retrieval", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/remote_retrieval/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/remote_retrieval/framework/mastra-ai.md", "updated_at": "2026-05-12T10:23:41.560Z" } ``` ## Introduction This guide walks you through connecting Remote retrieval to Mastra AI using the Composio tool router. By the end, you'll have a working Remote retrieval agent that can show all pending laptop return orders, get company info for acme corp, validate your remote retrieval api key through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Remote retrieval account through Composio's Remote retrieval MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Remote retrieval with - [OpenAI Agents SDK](https://composio.dev/toolkits/remote_retrieval/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/remote_retrieval/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/remote_retrieval/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/remote_retrieval/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/remote_retrieval/framework/codex) - [OpenClaw](https://composio.dev/toolkits/remote_retrieval/framework/openclaw) - [Hermes](https://composio.dev/toolkits/remote_retrieval/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/remote_retrieval/framework/cli) - [Google ADK](https://composio.dev/toolkits/remote_retrieval/framework/google-adk) - [LangChain](https://composio.dev/toolkits/remote_retrieval/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/remote_retrieval/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/remote_retrieval/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/remote_retrieval/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 Remote retrieval tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch Remote retrieval 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 Remote retrieval 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 Remote retrieval MCP server, and what's possible with it? The Remote retrieval MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Remote retrieval account. It provides structured and secure access to your company’s equipment logistics, so your agent can perform actions like listing equipment return orders, validating API access, and fetching company details on your behalf. - Comprehensive order tracking and listing: Ask your agent to retrieve a paginated list of all equipment return orders, with optional filters for status or date to keep tabs on ongoing returns. - Company information retrieval: Let your agent pull detailed company information instantly, helping with audits, reporting, or support workflows. - API key validation automation: Have your agent confirm that your API key is valid before performing sensitive actions, ensuring secure and authorized access every time. - Status-based filtering of return orders: Easily filter and fetch orders by their current status (e.g., pending, completed) to streamline logistics reviews or escalation processes. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `REMOTE_RETRIEVAL_CREATE_ORDER` | Create Order | Tool to create IT asset retrieval orders for remote employees. Use when you need to schedule pickup of laptops, monitors, cell phones, or tablets from employees. Supports both return-to-company and recycle-with-data-destruction workflows. | | `REMOTE_RETRIEVAL_GET_ALL_ORDERS` | Get All Orders | Tool to retrieve a paginated list of all orders. Use when you need to list orders with optional filters like status or dates. Call after authentication. | | `REMOTE_RETRIEVAL_GET_COMPANY_DETAILS` | Get Company Details | Tool to retrieve detailed information for a company. Use after confirming a valid company_id. | | `REMOTE_RETRIEVAL_GET_DEVICE_PRICES` | Get Device Prices | Tool to retrieve real-time pricing data for all supported devices. Use when you need current prices for Laptop, Monitor (17-23 inch), Monitor_27 (24-27 inch), Tablet, or Cell Phone. | | `REMOTE_RETRIEVAL_GET_ORDER_DETAILS` | Get Order Details | Tool to retrieve specific order details by order ID. Use when you need detailed information about an order including employee info, company info, and shipment status (device_type, send_status, return_status). | | `REMOTE_RETRIEVAL_LIST_PENDING_ORDERS` | List Pending Orders | Tool to retrieve list of all pending orders. Use when you need to check orders awaiting payment completion. Results are paginated up to 25 per page. | | `REMOTE_RETRIEVAL_VALIDATE_USER` | RemoteRetrieval: Validate User | Tool to validate the provided API key. Use when you need to confirm the API key's validity. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Remote retrieval MCP server is an implementation of the Model Context Protocol that connects your AI agent to Remote retrieval. It provides structured and secure access so your agent can perform Remote retrieval 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 Remote retrieval 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 Remote retrieval What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "remote_retrieval" for Remote retrieval 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: ["remote_retrieval"], }, ); const composioMCPUrl = session.mcp.url; console.log("Remote retrieval 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 Remote retrieval 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: "remote_retrieval-mastra-agent", instructions: "You are an AI agent with Remote retrieval 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 Remote retrieval 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: { remote_retrieval: 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: ["remote_retrieval"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { remote_retrieval: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "remote_retrieval-mastra-agent", instructions: "You are an AI agent with Remote retrieval 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: { remote_retrieval: 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 Remote retrieval 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 Remote retrieval MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/remote_retrieval/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/remote_retrieval/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/remote_retrieval/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/remote_retrieval/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/remote_retrieval/framework/codex) - [OpenClaw](https://composio.dev/toolkits/remote_retrieval/framework/openclaw) - [Hermes](https://composio.dev/toolkits/remote_retrieval/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/remote_retrieval/framework/cli) - [Google ADK](https://composio.dev/toolkits/remote_retrieval/framework/google-adk) - [LangChain](https://composio.dev/toolkits/remote_retrieval/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/remote_retrieval/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/remote_retrieval/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/remote_retrieval/framework/crew-ai) ## Related Toolkits - [Ashby](https://composio.dev/toolkits/ashby) - Ashby is an applicant tracking system that handles job postings, candidate management, and hiring analytics. - [Async interview](https://composio.dev/toolkits/async_interview) - Async interview is an on-demand video interview platform for streamlined hiring. Candidates record responses on their schedule, so employers can review anytime. - [Bamboohr](https://composio.dev/toolkits/bamboohr) - BambooHR is a cloud-based HR management platform for small and mid-sized businesses. It streamlines employee data, HR workflows, and reporting in one easy interface. - [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date. - [Connecteam](https://composio.dev/toolkits/connecteam) - Connecteam is a workforce management platform for deskless teams, streamlining operations, HR, and team communication. It helps businesses save time by automating scheduling, time tracking, and staff engagement tasks. - [Lever](https://composio.dev/toolkits/lever) - Lever is an applicant tracking system that blends sourcing, CRM, and analytics for recruiting. It helps companies scale hiring with collaborative workflows and actionable insights. - [Recruitee](https://composio.dev/toolkits/recruitee) - Recruitee is collaborative hiring software that centralizes recruitment tasks for teams. It streamlines sourcing, interviewing, and hiring so you can fill roles faster. - [Sap successfactors](https://composio.dev/toolkits/sap_successfactors) - Sap successfactors is a cloud-based human capital management suite for HR, payroll, recruiting, and talent management. It helps organizations centralize employee data and streamline the entire employee lifecycle. - [Talenthr](https://composio.dev/toolkits/talenthr) - TalentHR is an intuitive, all-in-one HR tool for managing employee records, leave, and HR workflows. It streamlines HR operations so businesses can focus on people, not paperwork. - [Workable](https://composio.dev/toolkits/workable) - Workable is an all-in-one HR software platform that streamlines hiring, employee management, and payroll. It helps teams simplify recruiting, onboarding, and staff operations in one place. - [Workday](https://composio.dev/toolkits/workday) - Workday is a cloud-based ERP platform for HR, finance, and workforce analytics. It streamlines employee management, payroll, and business operations in a single system. - [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable. - [Google Calendar](https://composio.dev/toolkits/googlecalendar) - Google Calendar is a time management service for scheduling meetings, events, and reminders. It streamlines personal and team organization with integrated notifications and sharing options. - [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. - [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management. - [Twitter](https://composio.dev/toolkits/twitter) - Twitter is a social media platform for sharing real-time updates, conversations, and news. Stay connected, informed, and engaged with communities worldwide. - [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. - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [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. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Remote retrieval MCP? With a standalone Remote retrieval MCP server, the agents and LLMs can only access a fixed set of Remote retrieval tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Remote retrieval 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 Remote retrieval tools. ### Can I manage the permissions and scopes for Remote retrieval while using Tool Router? Yes, absolutely. You can configure which Remote retrieval 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 Remote retrieval data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)