# How to integrate Calendly MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Calendly MCP with Vercel AI SDK v6", "toolkit": "Calendly", "toolkit_slug": "calendly", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/calendly/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/calendly/framework/ai-sdk.md", "updated_at": "2026-05-12T10:04:47.950Z" } ``` ## Introduction This guide walks you through connecting Calendly to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Calendly agent that can create a single-use scheduling link for your next meeting, cancel your 2pm event with a reason, mark an invitee as no-show for today's appointment through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Calendly account through Composio's Calendly MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Calendly with - [ChatGPT](https://composio.dev/toolkits/calendly/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/calendly/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/calendly/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/calendly/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/calendly/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/calendly/framework/codex) - [Cursor](https://composio.dev/toolkits/calendly/framework/cursor) - [VS Code](https://composio.dev/toolkits/calendly/framework/vscode) - [OpenCode](https://composio.dev/toolkits/calendly/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/calendly/framework/openclaw) - [Hermes](https://composio.dev/toolkits/calendly/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/calendly/framework/cli) - [Google ADK](https://composio.dev/toolkits/calendly/framework/google-adk) - [LangChain](https://composio.dev/toolkits/calendly/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/calendly/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/calendly/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/calendly/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Calendly integration - Using Composio's Tool Router to dynamically load and access Calendly 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 Calendly MCP server, and what's possible with it? The Calendly MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Calendly account. It provides structured and secure access to your scheduling workflows, so your agent can perform actions like creating personalized scheduling links, managing events, handling invitee statuses, and automating reminders on your behalf. - Instant scheduling link creation: Direct your agent to generate single-use or shareable scheduling links so others can book time with you instantly—no more back-and-forth emails. - Automated event and invitee management: Have your agent cancel events, mark invitees as no-shows, or remove no-show statuses to keep your calendar accurate and up to date. - Custom one-off event setup: Empower your agent to create unique, one-off meeting types for special situations, bypassing your regular availability rules. - Webhook subscription automation: Let the agent set up webhook subscriptions to trigger notifications or workflows in real time when events happen in your Calendly account. - Data privacy and compliance actions: Instruct your agent to delete invitee data or scheduled event records as needed for privacy or regulatory compliance, especially for enterprise use cases. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `CALENDLY_CANCEL_SCHEDULED_EVENT` | Cancel scheduled event | Tool to cancel a scheduled Calendly event by creating a cancellation record. Use when you need to permanently cancel an existing, active event. The cancellation will trigger notifications to all invitees. | | `CALENDLY_CREATE_EVENT_TYPE` | Create Event Type | Tool to create a new one-on-one event type (kind: solo) in Calendly. Use when you need to programmatically create a new event type for scheduling meetings. | | `CALENDLY_CREATE_ONE_OFF_EVENT_TYPE` | Create One-Off Event Type | Creates a temporary Calendly one-off event type for unique meetings outside regular availability, requiring valid host/co-host URIs, a future date/range for `date_setting`, and a positive `duration`. | | `CALENDLY_CREATE_SCHEDULING_LINK` | Create scheduling link | Create a single-use scheduling link. Creates a scheduling link that can be used to book an event. The link allows invitees to schedule up to the specified maximum number of events. Once the limit is reached, the link becomes inactive. | | `CALENDLY_CREATE_SHARE` | Create share | Creates a customizable, one-time share link for a Calendly event type, allowing specific overrides to its settings (e.g., duration, availability, location) without altering the original event type. | | `CALENDLY_CREATE_SINGLE_USE_SCHEDULING_LINK` | Create single use scheduling link | Creates a one-time, single-use scheduling link for an active Calendly event type, expiring after one booking. | | `CALENDLY_CREATE_WEBHOOKS` | Create webhook subscription | Tool to create a webhook subscription for receiving Calendly event notifications. Use when you need to set up automated notifications for events like meeting bookings or cancellations. Organization scope triggers webhooks for all events organization-wide, while user/group scopes limit triggering to specific users or groups. | | `CALENDLY_DELETE_INVITEE_DATA` | Delete invitee data | Permanently removes all invitee data associated with the provided emails from past organization events, for data privacy compliance (requires Enterprise subscription; deletion may take up to one week). | | `CALENDLY_DELETE_INVITEE_NO_SHOW` | Delete invitee no show | Deletes an Invitee No-Show record by its `uuid` to reverse an invitee's 'no-show' status; the `uuid` must refer to an existing record. | | `CALENDLY_DELETE_ORGANIZATION_MEMBERSHIP` | Delete organization membership | Tool to remove a user from a Calendly organization by membership UUID. Use when you need to revoke a user's access to an organization. Requires admin rights; organization owners cannot be removed. | | `CALENDLY_DELETE_SCHEDULED_EVENT_DATA` | Delete scheduled event data | For Enterprise users, initiates deletion of an organization's scheduled event data between a `start_time` and `end_time` (inclusive, where `start_time` must be <= `end_time`); actual data deletion may take up to 7 days to complete. | | `CALENDLY_DELETE_WEBHOOK_SUBSCRIPTION` | Delete webhook subscription | Deletes an existing webhook subscription to stop Calendly sending event notifications to its registered callback URL; this operation is idempotent. | | `CALENDLY_GET_EVENT` | Get event | Use to retrieve a specific Calendly scheduled event by its UUID, provided the event exists in the user's Calendly account. | | `CALENDLY_GET_EVENT_INVITEE` | Get event invitee | Retrieves detailed information about a specific invitee of a scheduled event, using their unique UUIDs. | | `CALENDLY_GET_EVENT_TYPE` | Get event type | Retrieves details for a specific Calendly event type, identified by its UUID, which must be valid and correspond to an existing event type. | | `CALENDLY_GET_EVENT_TYPE_AVAILABILITY` | Get event type availability | Tool to retrieve availability schedules configured for a specific Calendly event type. Use when you need to get the availability rules including day-of-week schedules and date-specific overrides. | | `CALENDLY_GET_GROUP` | Get group | Retrieves all attributes of a specific Calendly group by its UUID; the group must exist. | | `CALENDLY_GET_GROUP_RELATIONSHIP` | Get group relationship | Retrieves a specific Calendly group relationship by its valid and existing UUID, providing details on user-group associations and membership. | | `CALENDLY_GET_INVITEE_NO_SHOW` | Get invitee no show | Retrieves details for a specific Invitee No Show record by its UUID; an Invitee No Show is marked when an invitee does not attend a scheduled event. | | `CALENDLY_GET_ORGANIZATION` | Get organization | Tool to retrieve information about a specific Calendly organization. Use when you need to get organization details such as name, slug, or timestamps. | | `CALENDLY_GET_ORGANIZATION_INVITATION` | Get organization invitation | Retrieves a specific Calendly organization invitation using its UUID and the parent organization's UUID. | | `CALENDLY_GET_ORGANIZATION_MEMBERSHIP` | Get organization membership | Retrieves a specific Calendly organization membership by its UUID, returning all its attributes. | | `CALENDLY_GET_ROUTING_FORM` | Get routing form | Retrieves a specific routing form by its UUID, providing its configuration details including questions and routing logic. | | `CALENDLY_GET_ROUTING_FORM_SUBMISSION` | Get routing form submission | Tool to retrieve details about a specific routing form submission by its UUID. Use when you need submission details including questions, answers, and routing results. | | `CALENDLY_GET_SAMPLE_WEBHOOK_DATA` | Get sample webhook data | Tool to retrieve sample webhook payload data for testing webhook subscriptions. Use when you need to verify webhook setup and understand the data structure before creating actual webhook subscriptions. | | `CALENDLY_GET_USER` | Get user | Retrieves comprehensive details for an existing Calendly user. | | `CALENDLY_GET_USER_AVAILABILITY_SCHEDULE` | Get user availability schedule | Retrieves an existing user availability schedule by its UUID; this schedule defines the user's default hours of availability. | | `CALENDLY_GET_WEBHOOK_SUBSCRIPTION` | Get webhook subscription | Retrieves the details of an existing webhook subscription, identified by its UUID, including its callback URL, subscribed events, scope, and state. | | `CALENDLY_INVITEE_NO_SHOW` | Mark invitee as no-show | Tool to mark an invitee as a no-show for a scheduled event. Use when an invitee fails to attend their scheduled meeting and you need to record their absence in Calendly. | | `CALENDLY_LIST_ACTIVITY_LOG_ENTRIES` | List activity log entries | Retrieves a list of activity log entries for a specified Calendly organization (requires an active Enterprise subscription), supporting filtering, sorting, and pagination. | | `CALENDLY_LIST_EVENT_INVITEES` | List event invitees | Retrieves a list of invitees for a specified Calendly event UUID, with options to filter by status or email, and sort by creation time. | | `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` | List event type available times | Fetches available time slots for a Calendly event type within a specified time range; results are not paginated. | | `CALENDLY_LIST_EVENT_TYPE_MEMBERSHIPS` | List event type hosts | Tool to retrieve a list of event type hosts (memberships) for a specific event type. Use when you need to see which users are configured as hosts for an event type. | | `CALENDLY_LIST_EVENT_TYPES` | List Event Types | Tool to list all Event Types associated with a specified User or Organization. Use when you need to retrieve event types for a user or organization. Use scheduling_url from results directly; do not manually construct event type URLs. | | `CALENDLY_LIST_GROUP_RELATIONSHIPS` | List group relationships | Retrieves a list of group relationships defining an owner's role (e.g., member, admin) within a group; an owner can have one membership per group but multiple admin roles across different groups. | | `CALENDLY_LIST_GROUPS` | List groups | Returns a list of groups for a specified Calendly organization URI, supporting pagination. | | `CALENDLY_LIST_ORGANIZATION_INVITATIONS` | List organization invitations | Retrieves a list of invitations for a specific organization, identified by its UUID. | | `CALENDLY_LIST_ORGANIZATION_MEMBERSHIPS` | List organization memberships | Retrieves a list of organization memberships. | | `CALENDLY_LIST_OUTGOING_COMMUNICATIONS` | List outgoing communications | Retrieves a list of outgoing SMS communications for a specified organization; requires an Enterprise subscription and if filtering by creation date, both `min_created_at` and `max_created_at` must be provided to form a valid range. | | `CALENDLY_LIST_ROUTING_FORMS` | List routing forms | Retrieves routing forms for a specified organization; routing forms are questionnaires used to direct invitees to appropriate booking pages or external URLs. | | `CALENDLY_LIST_SCHEDULED_EVENTS` | List scheduled events | Tool to retrieve a list of scheduled Calendly events. Use when you need to view events for a specific user, organization, or group. Requires exactly one of user, organization, or group parameter to scope the query. | | `CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES` | List user availability schedules | Retrieves all availability schedules for the specified Calendly user. | | `CALENDLY_LIST_USER_BUSY_TIMES` | List user busy times | Fetches a user's busy time intervals (internal and external calendar events) in ascending order for a period up to 7 days; keyset pagination is not supported. | | `CALENDLY_LIST_USER_LOCATIONS` | List User Meeting Locations | Tool to retrieve configured meeting location information for a given Calendly user. Use when you need to see all available location options configured by a user for their meetings. | | `CALENDLY_LIST_WEBHOOK_SUBSCRIPTIONS` | List webhook subscriptions | Retrieves webhook subscriptions for a Calendly organization; `scope` determines if `user` or `group` URI is also required for filtering. | | `CALENDLY_ORGANIZATION_INVITATION` | Invite user to organization | Tool to invite a user to a Calendly organization via email. Use when you need to send an organization invitation to a new user. Requires organization owner or admin privileges. | | `CALENDLY_POST_INVITEE` | Create Event Invitee | Tool to create a new Event Invitee with standard notifications, calendar invites, reschedules, and workflows. Use when programmatically scheduling meetings via API. Requires paid Calendly plan (Standard+). | | `CALENDLY_REMOVE_USER_FROM_ORGANIZATION` | Remove user from organization | Removes a user (who is not an owner) from an organization by their membership UUID, requiring administrative privileges. | | `CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION` | Revoke a user's organization invitation | Revokes a pending and revokable (not yet accepted or expired) organization invitation using its UUID and the organization's UUID, rendering the invitation link invalid. | | `CALENDLY_UPDATE_EVENT_TYPE` | Update Event Type | Tool to update an existing one-on-one event type (kind: solo) in Calendly. Use when you need to modify event type settings such as name, duration, location, or description. NOTE: Currently only supports one-on-one event types. | | `CALENDLY_UPDATE_EVENT_TYPE_AVAILABILITY` | Update Event Type Availability | Tool to update an event type availability schedule in Calendly. Use when you need to change the timezone or availability rules for an event type. WARNING: Updating rules will overwrite all existing rules - retrieve existing rules first using GET /event_type_availability_schedules. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Calendly MCP server is an implementation of the Model Context Protocol that connects your AI agent to Calendly. It provides structured and secure access so your agent can perform Calendly 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 Calendly 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 Calendly-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: ["calendly"], }); 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 Calendly 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 calendly, 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 Calendly 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: ["calendly"], }); 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 calendly, 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 Calendly 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 Calendly MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/calendly/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/calendly/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/calendly/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/calendly/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/calendly/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/calendly/framework/codex) - [Cursor](https://composio.dev/toolkits/calendly/framework/cursor) - [VS Code](https://composio.dev/toolkits/calendly/framework/vscode) - [OpenCode](https://composio.dev/toolkits/calendly/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/calendly/framework/openclaw) - [Hermes](https://composio.dev/toolkits/calendly/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/calendly/framework/cli) - [Google ADK](https://composio.dev/toolkits/calendly/framework/google-adk) - [LangChain](https://composio.dev/toolkits/calendly/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/calendly/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/calendly/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/calendly/framework/crew-ai) ## Related Toolkits - [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. - [Apaleo](https://composio.dev/toolkits/apaleo) - Apaleo is a cloud-based property management platform for hospitality businesses. It centralizes reservations, billing, and daily operations for smoother hotel management. - [Appointo](https://composio.dev/toolkits/appointo) - Appointo is an appointment booking platform for Shopify stores. It lets businesses add online scheduling to their websites with zero coding. - [Bart](https://composio.dev/toolkits/bart) - Bart is the Bay Area Rapid Transit system, providing fast public transportation across the San Francisco Bay Area. It helps commuters and travelers get real-time schedule info, plan routes, and stay updated on service changes. - [Bookingmood](https://composio.dev/toolkits/bookingmood) - Bookingmood is commission-free booking software for rental businesses. It lets you manage reservations and sync bookings directly on your website. - [Booqable](https://composio.dev/toolkits/booqable) - Booqable is a rental software platform for managing inventory, bookings, and reservations. It helps businesses streamline rentals and keep track of every item with ease. - [Cal](https://composio.dev/toolkits/cal) - Cal is a meeting scheduling platform that offers shareable booking links and real-time calendar syncing. It streamlines the process of finding mutual availability to make scheduling effortless. - [Calendarhero](https://composio.dev/toolkits/calendarhero) - Calendarhero is a powerful scheduling platform that streamlines your calendar management across multiple services. It helps you efficiently schedule, reschedule, and organize meetings without the back-and-forth. - [Etermin](https://composio.dev/toolkits/etermin) - eTermin is an online appointment scheduling platform for businesses to manage bookings. It streamlines client appointments, saving time and reducing scheduling conflicts. - [Evenium](https://composio.dev/toolkits/evenium) - Evenium is an all-in-one platform for managing professional events, from planning to analysis. It helps teams simplify event logistics, boost engagement, and track every detail in one place. - [Eventee](https://composio.dev/toolkits/eventee) - Eventee is a user-friendly event management platform for mobile and web. It boosts attendee engagement for in-person, virtual, and hybrid events. - [Eventzilla](https://composio.dev/toolkits/eventzilla) - Eventzilla is an event management platform for creating, promoting, and running events. It streamlines ticketing, registration, and attendee coordination for organizers. - [Humanitix](https://composio.dev/toolkits/humanitix) - Humanitix is a not-for-profit ticketing platform that donates 100% of profits to charity. It empowers event organizers to make social impact with every ticket sold. - [Lodgify](https://composio.dev/toolkits/lodgify) - Lodgify is an all-in-one vacation rental software for property managers and owners. It centralizes bookings, guest messaging, and channel synchronization in one dashboard. - [Planyo Online Booking](https://composio.dev/toolkits/planyo_online_booking) - Planyo Online Booking is a flexible reservation system for managing bookings by day, hour, or event. It streamlines scheduling for any business needing reservations. - [Scheduleonce](https://composio.dev/toolkits/scheduleonce) - Scheduleonce is a scheduling platform for capturing, qualifying, and engaging with inbound leads. It streamlines appointment booking and follow-ups for faster lead conversion. - [Supersaas](https://composio.dev/toolkits/supersaas) - Supersaas is a flexible appointment scheduling platform for businesses and individuals. It streamlines bookings, reminders, and calendar management in one place. - [Sympla](https://composio.dev/toolkits/sympla) - Sympla is a platform for managing in-person and online events, ticket sales, and registrations. It streamlines event setup, attendee tracking, and digital content delivery. - [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 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. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Calendly MCP? With a standalone Calendly MCP server, the agents and LLMs can only access a fixed set of Calendly tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Calendly 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 Calendly tools. ### Can I manage the permissions and scopes for Calendly while using Tool Router? Yes, absolutely. You can configure which Calendly 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 Calendly data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)