# How to integrate Zoom MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Zoom MCP with Vercel AI SDK v6", "toolkit": "Zoom", "toolkit_slug": "zoom", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/zoom/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/zoom/framework/ai-sdk.md", "updated_at": "2026-05-06T08:35:09.616Z" } ``` ## Introduction This guide walks you through connecting Zoom to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Zoom agent that can schedule a zoom meeting for tomorrow, add a registrant to your next webinar, summarize your last recorded meeting through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Zoom account through Composio's Zoom MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Zoom with - [ChatGPT](https://composio.dev/toolkits/zoom/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/zoom/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/zoom/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/zoom/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/zoom/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/zoom/framework/codex) - [Cursor](https://composio.dev/toolkits/zoom/framework/cursor) - [VS Code](https://composio.dev/toolkits/zoom/framework/vscode) - [OpenCode](https://composio.dev/toolkits/zoom/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/zoom/framework/openclaw) - [Hermes](https://composio.dev/toolkits/zoom/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/zoom/framework/cli) - [Google ADK](https://composio.dev/toolkits/zoom/framework/google-adk) - [LangChain](https://composio.dev/toolkits/zoom/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/zoom/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/zoom/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/zoom/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Zoom integration - Using Composio's Tool Router to dynamically load and access Zoom tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## What is the Zoom MCP server, and what's possible with it? The Zoom MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Zoom account. It provides structured and secure access to your meetings, webinars, and usage data, so your agent can schedule meetings, register attendees, retrieve recordings, summarize sessions, and analyze participant engagement on your behalf. - Automated meeting scheduling and management: Instruct your agent to create new Zoom meetings, fetch details for upcoming or past meetings, and manage all your session logistics effortlessly. - Seamless participant and registrant registration: Have your agent add attendees or registrants to meetings and webinars, handling all required information and permissions automatically. - On-demand access to recordings and summaries: Let your agent retrieve meeting recordings or generate AI-powered meeting summaries, making it easy to review or share past sessions. - Insightful participant analytics: Ask your agent to fetch detailed lists of past meeting participants or generate daily usage reports, helping you track engagement and attendance trends. - Efficient recording and data cleanup: Direct your agent to delete outdated recordings or manage your Zoom storage, keeping your account streamlined and organized. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `ZOOM_ADD_A_MEETING_REGISTRANT` | Add a meeting registrant | This text guides on creating and customizing a user's registration for a zoom meeting, with a max of 4,999 registrants. preconditions include the host being licensed. api scopes and a light rate limit apply. | | `ZOOM_ADD_A_WEBINAR_REGISTRANT` | Add a webinar registrant | Zoom users with a webinar plan can create and manage webinars, broadcasting to up to 10,000 attendees. registration requires a pro plan, specific permissions, and is governed by a "light" rate limit. | | `ZOOM_CREATE_A_MEETING` | Create a meeting | Enable zoom meeting creation via user-level apps with "me". "start url" for hosts expires in 2 hours, or 90 days for "custcreate" users. renew via api, capped at 100 requests/day. requires "meeting:write" permission, subject to medium rate limit. | | `ZOOM_DELETE_MEETING_RECORDINGS` | Delete meeting recordings | Summary: to delete all meeting recordings, ensure the user's account has cloud recording enabled. required permissions include `recording:write:admin` and `recording:write` with a `light` rate limit label. | | `ZOOM_GET_A_MEETING` | Get a meeting | The text provides details on api permissions for reading meeting information, categorizing permissions into general and granular scopes, and labels the rate limit as 'light'. | | `ZOOM_GET_A_MEETING_SUMMARY` | Get a meeting summary | Meeting summary info requires a pro+ host plan, ai companion enabled, excluding e2ee meetings. scopes include meeting summary:read and admin versions. rate limit: light. | | `ZOOM_GET_A_WEBINAR` | Get a webinar | Access zoom webinar details requires pro or higher plan and webinar add-on. scopes include `webinar:read:admin` and `webinar:read`. granular scopes and a 'light' rate limit also apply. | | `ZOOM_GET_DAILY_USAGE_REPORT` | Get daily usage report | The daily report provides zoom service usage details, like new users, meetings, participants, and minutes per day for a month, requiring a pro plan or higher. it has a 'heavy' rate limit. | | `ZOOM_GET_MEETING_RECORDINGS` | Get meeting recordings | To download meeting recordings, use `download url`. include oauth token in the header for passcode-protected ones. supports `recording:read` and `phone recording:read:admin` scopes, with a `light` rate limit. | | `ZOOM_GET_PAST_MEETING_PARTICIPANTS` | Get past meeting participants | Api allows paid users (pro+) to fetch past meeting attendee info, excluding solo participants. requires double encoding for certain uuids, with `meeting:read` scope and others. rate limit is medium. | | `ZOOM_LIST_ALL_RECORDINGS` | List all recordings | This text details how to list zoom cloud recordings for a user, notably by using "me" for user-level apps and requiring an oauth token for access. it requires a pro plan, cloud recording enabled, and has a medium rate limit. | | `ZOOM_LIST_ARCHIVED_FILES` | List archived files | Zoom's archiving solution enables administrators to automatically record and archive meeting data to third-party platforms for compliance, needing the meeting and webinar archiving feature enabled. | | `ZOOM_LIST_DEVICES` | List devices | This api lets you list devices. **scopes:** `device:read:admin`,`device:write:admin` **[rate limit label](https://marketplace.zoom.us/docs/api-reference/rate-limits#rate-limits):** `heavy` | | `ZOOM_LIST_MEETINGS` | List meetings | This zoom api lists a user's scheduled meetings using the `me` value for user-level apps, excluding instant meetings and only showing unexpired ones. it requires specific scopes and has a `medium` rate limit. | | `ZOOM_LIST_WEBINAR_PARTICIPANTS` | List webinar participants | Get a list of past webinar participants with a pro plan or above plus an add-on. requires specific scopes and has a medium rate limit. | | `ZOOM_LIST_WEBINARS` | List webinars | The api lists all scheduled webinars for zoom users with a webinar plan, using `me` for user-level apps. it only shows unexpired webinars for hosts broadcasting to up to 10,000 attendees. requires pro plan upwards and specific scopes. rate limit: medium. | | `ZOOM_UPDATE_A_MEETING` | Update a meeting | To update a meeting via api, ensure `start time` is future-dated; `recurrence` is needed. limit: 100 requests/day, 100 updates/meeting in 24 hrs. requires `meeting:write` and `meeting:write:admin` scopes, with a `light` rate limit. | ## Supported Triggers | Trigger slug | Name | Description | |---|---|---| | `ZOOM_DAILY_USAGE_REPORT_CHANGED_TRIGGER` | Daily Usage Report Changed | Triggers when the Zoom daily usage report changes for a selected year/month. This trigger monitors daily usage statistics including: - New users added - Number of meetings held - Participant counts - Meeting minutes consumed | | `ZOOM_MEETING_DETAILS_CHANGED_TRIGGER` | Meeting Details Changed | Triggers when a specific meeting's details change. Detects changes such as: - Meeting topic changes - Agenda updates - Schedule changes (timezone, duration) - Settings modifications (waiting room, recording, video, etc.) - Password changes - Recurrence pattern updates | | `ZOOM_MEETING_RECORDING_CHANGED_TRIGGER` | Meeting Recording Changed | Triggers when a specific meeting's cloud recordings change. Detects changes such as: - New recording files appearing - Recording processing completion (status changes) - Recording metadata changes (count, size, etc.) - New participant audio files | | `ZOOM_MEETING_SUMMARY_UPDATED_TRIGGER` | Meeting Summary Created or Updated | Triggers when a meeting summary is created or updated for a specific meeting. IMPORTANT: This trigger requires a PAID Zoom account (Pro, Business, or Enterprise plan). Free Zoom accounts cannot use this feature. Additionally requires: - AI Companion feature enabled in account settings - Meeting must not be end-to-end encrypted (E2EE) - Meeting summary must be enabled and generated for the meeting | | `ZOOM_NEW_CLOUD_RECORDING_TRIGGER` | New Cloud Recording | Triggers when a new cloud recording meeting instance appears for a user. | | `ZOOM_NEW_MEETING_CREATED_TRIGGER` | New Meeting Created | Triggers when a new Zoom meeting is created for a user. | | `ZOOM_NEW_MEETING_PARTICIPANT_TRIGGER` | New Meeting Participant | Triggers when a new participant appears in a past meeting's participant report. | | `ZOOM_NEW_WEBINAR_CREATED_TRIGGER` | New Webinar Created | Triggers when a new webinar is created for a user. | | `ZOOM_NEW_WEBINAR_PARTICIPANT_TRIGGER` | New Webinar Participant | Triggers when a new participant appears in a past webinar's participant list. | | `ZOOM_USER_INFORMATION_CHANGED_TRIGGER` | User Information Changed | Triggers when a Zoom user's information changes. Detects changes such as: - Profile information updates (name, email, display name) - Role or type changes - Department, job title, or location updates - Contact information changes (phone, timezone) - Status changes (active, inactive, pending) - Settings updates (language, pronouns, etc.) | | `ZOOM_WEBINAR_DETAILS_CHANGED_TRIGGER` | Webinar Details Changed | Triggers when a Zoom webinar's details change. Detects changes such as: - Topic updates - Start time changes - Agenda modifications - Duration changes - Settings updates (host video, registration type, audio options, etc.) - Status changes - Occurrence updates for recurring webinars - Recurrence pattern changes | ## Creating MCP Server - Stand-alone vs Composio SDK The Zoom MCP server is an implementation of the Model Context Protocol that connects your AI agent to Zoom. It provides structured and secure access so your agent can perform Zoom 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 you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 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'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) 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, }); ``` ### 5. Create Tool Router session and initialize MCP client What's happening: - We're creating a Tool Router session that gives your agent access to Zoom tools - The create method takes the user ID and specifies which toolkits should be available - The returned mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Zoom-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["zoom"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Zoom tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to zoom, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Zoom tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript 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({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); 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 { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) 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, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["zoom"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to zoom, like summarize my last 5 emails, send an email, etc... :)))\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({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Zoom agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Zoom MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/zoom/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/zoom/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/zoom/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/zoom/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/zoom/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/zoom/framework/codex) - [Cursor](https://composio.dev/toolkits/zoom/framework/cursor) - [VS Code](https://composio.dev/toolkits/zoom/framework/vscode) - [OpenCode](https://composio.dev/toolkits/zoom/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/zoom/framework/openclaw) - [Hermes](https://composio.dev/toolkits/zoom/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/zoom/framework/cli) - [Google ADK](https://composio.dev/toolkits/zoom/framework/google-adk) - [LangChain](https://composio.dev/toolkits/zoom/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/zoom/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/zoom/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/zoom/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 Zoom MCP? With a standalone Zoom MCP server, the agents and LLMs can only access a fixed set of Zoom tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Zoom and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 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 Zoom tools. ### Can I manage the permissions and scopes for Zoom while using Tool Router? Yes, absolutely. You can configure which Zoom 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 Zoom data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)