# How to integrate Webex MCP with Mastra AI ```json { "title": "How to integrate Webex MCP with Mastra AI", "toolkit": "Webex", "toolkit_slug": "webex", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/webex/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/webex/framework/mastra-ai.md", "updated_at": "2026-05-12T10:30:09.836Z" } ``` ## Introduction This guide walks you through connecting Webex to Mastra AI using the Composio tool router. By the end, you'll have a working Webex agent that can create a new project discussion room, list all teams i am part of, send a meeting summary to your team through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Webex account through Composio's Webex MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Webex with - [ChatGPT](https://composio.dev/toolkits/webex/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/webex/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/webex/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/webex/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/webex/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/webex/framework/codex) - [Cursor](https://composio.dev/toolkits/webex/framework/cursor) - [VS Code](https://composio.dev/toolkits/webex/framework/vscode) - [OpenCode](https://composio.dev/toolkits/webex/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/webex/framework/openclaw) - [Hermes](https://composio.dev/toolkits/webex/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/webex/framework/cli) - [Google ADK](https://composio.dev/toolkits/webex/framework/google-adk) - [LangChain](https://composio.dev/toolkits/webex/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/webex/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/webex/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/webex/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 Webex tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch Webex 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 Webex 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 Webex MCP server, and what's possible with it? The Webex MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Webex account. It provides structured and secure access to your meetings, teams, rooms, and messaging, so your agent can perform actions like managing teams, creating rooms, posting messages, and handling memberships on your behalf. - Automated team and room management: Quickly create new teams or rooms, group conversations by topic, and keep collaboration spaces organized through your agent. - Seamless messaging and announcements: Direct your agent to post messages, send important files, or share updates with individuals or entire rooms instantly. - Membership and access control: Effortlessly add or remove members from teams and spaces, ensuring the right people have access at the right time. - Webhook and event integrations: List and manage Webex webhooks so your agent can react to events or changes as they happen in your workspace. - Content and message cleanup: Ask your agent to delete outdated or mistaken messages and memberships, keeping your workspace tidy and relevant. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `WEBEX_CREATE_TEAM` | Create Team | Creates a new Webex team and automatically adds the authenticated user as a member. Teams are used to organize and group multiple rooms (spaces) under a common umbrella. Use this when you need to create a collaborative workspace for a project, department, or any group that needs multiple related discussion spaces. Note: The creator is automatically added as a team member and can manage team memberships. Use the Team Memberships API to add additional members after creation. | | `WEBEX_GET_TEAM_DETAILS` | Get Team Details | Tool to retrieve details for a specific team by teamId. Use when you need full metadata of a team before performing team-related operations. | | `WEBEX_LIST_TEAMS` | List Teams | Lists all teams the authenticated user belongs to. Teams are groups of people with shared rooms visible to all members. Use this when you need to find available teams, get team IDs for other operations, or discover which teams a user has access to. Results are ordered by creation date (newest first) and can be paginated using the max parameter. | | `WEBEX_LIST_WEBHOOKS` | List Webhooks | Lists all webhooks registered for the authenticated user or organization. Supports optional filtering by maximum results and ownership type (creator vs org-wide). | | `WEBEX_MESSAGING_CREATE_MESSAGE` | Create Message | Tool to post a message to a Webex room or person. Use when you have a target roomId or private recipient and want to send text, markdown, files, or card attachments. | | `WEBEX_CREATE_ROOM` | Create Room | Creates a new Webex room for team collaboration. The authenticated user is automatically added as a member. Use this to create group rooms for team discussions or associate rooms with existing teams. To create a 1:1 room, use the Create Message action with toPersonId/toPersonEmail instead. Note: Team rooms cannot be moved after creation. Bots cannot simultaneously create and classify rooms. | | `WEBEX_MESSAGING_CREATE_TEAM_MEMBERSHIP` | Create Team Membership | Tool to add a person to a Webex team by personId or personEmail. Use when granting a user access to a team; requires teamId and one of personId or personEmail. | | `WEBEX_MESSAGING_DELETE_MEMBERSHIP` | Delete Membership | Tool to delete a Webex membership by its unique identifier. Use when you need to remove a member from a space after confirming the membership exists. Example: "Delete the membership with ID Y2lzY29zcGFjMDczNzA2Njg0ZDliY2YxNDE4NDQyYzQ5NDQzOTExYTk4". | | `WEBEX_MESSAGING_DELETE_MESSAGE` | Delete Message | Tool to delete a Webex message by its unique identifier. Use after confirming the messageId to remove unintended or obsolete messages. Example: "Delete the message with ID Y2lzY29zcGFyazovL21lc3NhZ2UvYWJjMTIzNDU2Nzg5". | | `WEBEX_MESSAGING_DELETE_ROOM` | Delete Room | Deletes a Webex room by its ID. Deleted rooms cannot be recovered. Note: Non-moderators will be removed from the room instead of deleting it (as a safety measure). Rooms that are part of a team will be archived instead of deleted. Use this when you need to permanently remove a room or leave a room. | | `WEBEX_MESSAGING_GET_MEMBERSHIP_DETAILS` | Get Membership Details | Tool to retrieve details for a specific membership. Use when you need metadata for a membership by its ID. | | `WEBEX_MESSAGING_GET_MESSAGE_DETAILS` | Get Message Details | Tool to retrieve details for a specific message. Use when you need full content and metadata by message ID. | | `WEBEX_MESSAGING_GET_TEAM_MEMBERSHIP_DETAILS` | Get Team Membership Details | Tool to retrieve details for a specific team membership. Use when you need metadata for a team membership by its ID. | | `WEBEX_MESSAGING_LIST_MEMBERSHIPS` | List Memberships | List memberships in Webex rooms. When called without parameters, returns memberships for all rooms the authenticated user belongs to. Use roomId to list all members of a specific room. Use personId or personEmail with roomId to check if a specific person is a member of a room. Supports filtering by teamId and limiting results with max parameter. | | `WEBEX_MESSAGING_LIST_MESSAGES` | List Messages | Tool to list messages in a room. Use when you need to retrieve chat history filtered by room, time window, or mentions. | | `WEBEX_MESSAGING_LIST_ROOMS` | List Rooms | Tool to list rooms the authenticated user belongs to. Use after authentication when needing to retrieve spaces filtered by team, type, or sorted. Example: "List my group rooms sorted by last activity." | | `WEBEX_MESSAGING_LIST_TEAM_MEMBERSHIPS` | List Team Memberships | Tool to list all memberships for a specific team. Use when you need to retrieve all members of a team, including their roles (moderator status). Requires a valid teamId. | | `WEBEX_PEOPLE_GET_PERSON` | Get Person Details | Retrieves detailed profile information for a specific person by their ID. Returns comprehensive user details including contact information, organizational data, presence status, and Webex Calling information. Use when you need full profile details for a known person ID. To find person IDs, use the List People action first. | | `WEBEX_PEOPLE_LIST_PEOPLE` | List People | Tool to list people in your organization. Use when you need to retrieve people filtered by email, display name, IDs, roles, or location. | | `WEBEX_ROOMS_GET_ROOM_DETAILS` | Get Room Details | Tool to retrieve details for a specific room. Use when you need full metadata of a room before posting messages or updating settings. | | `WEBEX_UPDATE_MEMBERSHIP` | Update Membership | Updates a Webex room membership by ID to change moderator or monitor status. Use this to grant or revoke moderator privileges, or to enable/disable room monitoring for a member. Note: Assigning moderator status requires special account permissions; operations may fail with 403 Forbidden if the authenticated user lacks the necessary entitlements. | | `WEBEX_UPDATE_ROOM` | Update Room | Update a room's title, lock status, or team association. The title parameter is always required by the Webex API - if you're only updating isLocked or teamId, you must still provide the current room title. | | `WEBEX_UPDATE_TEAM` | Update Team | Tool to update a team's name by teamId. Use when you need to rename a Webex team. Example: "Change team 12345 name to 'Project X Team'". | | `WEBEX_WEBHOOKS_CREATE_WEBHOOK` | Create Webhook | Creates a Webex webhook to receive real-time event notifications via HTTP POST requests to your specified URL. Use this tool to register for automated notifications when resources (messages, rooms, memberships, meetings, etc.) are created, updated, deleted, or undergo other state changes. Webhooks enable event-driven integrations without polling. Important: The webhook will be automatically disabled if your target URL fails to respond with HTTP 2xx status codes 100 times within five minutes. Requires 'read' scope for the monitored resource type. | | `WEBEX_WEBHOOKS_DELETE_WEBHOOK` | Delete Webhook | Tool to delete a specific webhook. Use when you need to remove an existing webhook by its ID after confirming the identifier. | | `WEBEX_WEBHOOKS_GET_WEBHOOK` | Get Webhook Details | Retrieves detailed information about a specific Webex webhook by its ID. Use this action to: - Inspect a webhook's configuration (target URL, resource, event type, filters) - Verify webhook status (active/inactive) - Check webhook ownership and security settings (secret, ownedBy) - Get webhook metadata (creation date, creator, organization) The webhook must exist and be accessible with your current credentials. Returns 404 error if the webhook ID is invalid or you don't have permission to view it. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Webex MCP server is an implementation of the Model Context Protocol that connects your AI agent to Webex. It provides structured and secure access so your agent can perform Webex 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 Webex 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 Webex What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "webex" for Webex 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: ["webex"], }, ); const composioMCPUrl = session.mcp.url; console.log("Webex 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 Webex 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: "webex-mastra-agent", instructions: "You are an AI agent with Webex 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 Webex 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: { webex: 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: ["webex"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { webex: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "webex-mastra-agent", instructions: "You are an AI agent with Webex 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: { webex: 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 Webex 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 Webex MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/webex/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/webex/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/webex/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/webex/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/webex/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/webex/framework/codex) - [Cursor](https://composio.dev/toolkits/webex/framework/cursor) - [VS Code](https://composio.dev/toolkits/webex/framework/vscode) - [OpenCode](https://composio.dev/toolkits/webex/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/webex/framework/openclaw) - [Hermes](https://composio.dev/toolkits/webex/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/webex/framework/cli) - [Google ADK](https://composio.dev/toolkits/webex/framework/google-adk) - [LangChain](https://composio.dev/toolkits/webex/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/webex/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/webex/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/webex/framework/crew-ai) ## Related Toolkits - [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. - [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. - [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place. - [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action. - [Microsoft teams](https://composio.dev/toolkits/microsoft_teams) - Microsoft Teams is a collaboration platform that combines chat, meetings, and file sharing within Microsoft 365. It keeps distributed teams connected and productive through seamless virtual communication. - [Slackbot](https://composio.dev/toolkits/slackbot) - Slackbot is a conversational automation tool for Slack that handles reminders, notifications, and automated responses. It boosts team productivity by streamlining onboarding, answering FAQs, and managing timely alerts—all right inside Slack. - [2chat](https://composio.dev/toolkits/_2chat) - 2chat is an API platform for WhatsApp and multichannel text messaging. It streamlines chat automation, group management, and real-time messaging for developers. - [Agent mail](https://composio.dev/toolkits/agent_mail) - Agent mail provides AI agents with dedicated email inboxes for sending, receiving, and managing emails. It empowers agents to communicate autonomously with people, services, and other agents—no human intervention needed. - [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place. - [Chatwork](https://composio.dev/toolkits/chatwork) - Chatwork is a team communication platform with group chats, file sharing, and task management. It helps businesses boost collaboration and streamline productivity. - [Clickmeeting](https://composio.dev/toolkits/clickmeeting) - ClickMeeting is a cloud-based platform for running online meetings and webinars. It helps businesses and individuals host, manage, and engage virtual audiences with ease. - [Confluence](https://composio.dev/toolkits/confluence) - Confluence is Atlassian's team collaboration and knowledge management platform. It helps your team organize, share, and update documents and project content in one secure workspace. - [Dailybot](https://composio.dev/toolkits/dailybot) - DailyBot streamlines team collaboration with chat-based standups, reminders, and polls. It keeps work flowing smoothly in your favorite messaging platforms. - [Dialmycalls](https://composio.dev/toolkits/dialmycalls) - Dialmycalls is a mass notification service for sending voice and text messages to contacts. It helps teams and organizations quickly broadcast urgent alerts and updates. - [Dialpad](https://composio.dev/toolkits/dialpad) - Dialpad is a cloud-based business phone and contact center system for teams. It unifies voice, video, messaging, and meetings across your devices. - [Discord](https://composio.dev/toolkits/discord) - Discord is a real-time messaging and VoIP platform for communities and teams. It lets users chat, share media, and collaborate across public and private channels. - [Discordbot](https://composio.dev/toolkits/discordbot) - Discordbot is an automation tool for Discord servers that handles moderation, messaging, and user engagement. It helps communities run smoothly by automating routine and complex tasks. - [Echtpost](https://composio.dev/toolkits/echtpost) - Echtpost is a secure digital communication platform for encrypted document and message exchange. It ensures confidential data stays private and protected during transmission. - [Egnyte](https://composio.dev/toolkits/egnyte) - Egnyte is a cloud-based platform for secure file sharing, storage, and governance. It helps teams collaborate efficiently while maintaining data compliance and security. - [Google Meet](https://composio.dev/toolkits/googlemeet) - Google Meet is a secure video conferencing platform for virtual meetings, chat, and screen sharing. It helps teams connect, collaborate, and communicate seamlessly from anywhere. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Webex MCP? With a standalone Webex MCP server, the agents and LLMs can only access a fixed set of Webex tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Webex 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 Webex tools. ### Can I manage the permissions and scopes for Webex while using Tool Router? Yes, absolutely. You can configure which Webex 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 Webex data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)