# How to integrate Calendarhero MCP with LangChain ```json { "title": "How to integrate Calendarhero MCP with LangChain", "toolkit": "Calendarhero", "toolkit_slug": "calendarhero", "framework": "LangChain", "framework_slug": "langchain", "url": "https://composio.dev/toolkits/calendarhero/framework/langchain", "markdown_url": "https://composio.dev/toolkits/calendarhero/framework/langchain.md", "updated_at": "2026-05-12T10:04:45.802Z" } ``` ## Introduction This guide walks you through connecting Calendarhero to LangChain using the Composio tool router. By the end, you'll have a working Calendarhero agent that can schedule a meeting with your project team, list all meetings i have this week, fetch details for your next scheduled meeting through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Calendarhero account through Composio's Calendarhero MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Calendarhero with - [OpenAI Agents SDK](https://composio.dev/toolkits/calendarhero/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/calendarhero/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/calendarhero/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/calendarhero/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/calendarhero/framework/codex) - [OpenClaw](https://composio.dev/toolkits/calendarhero/framework/openclaw) - [Hermes](https://composio.dev/toolkits/calendarhero/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/calendarhero/framework/cli) - [Google ADK](https://composio.dev/toolkits/calendarhero/framework/google-adk) - [Vercel AI SDK](https://composio.dev/toolkits/calendarhero/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/calendarhero/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/calendarhero/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/calendarhero/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get and set up your OpenAI and Composio API keys - Connect your Calendarhero project to Composio - Create a Tool Router MCP session for Calendarhero - Initialize an MCP client and retrieve Calendarhero tools - Build a LangChain agent that can interact with Calendarhero - Set up an interactive chat interface for testing ## What is LangChain? LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context. Key features include: - Agent Framework: Build agents that can use tools and make decisions - MCP Integration: Connect to external services through Model Context Protocol adapters - Memory Management: Maintain conversation history across interactions - Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers ## What is the Calendarhero MCP server, and what's possible with it? The Calendarhero MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Calendarhero account. It provides structured and secure access to your calendar management tools, so your agent can schedule meetings, manage contacts, fetch meeting details, and access your calendar integrations on your behalf. - Automated meeting scheduling and requests: Easily have your agent schedule new meetings, select participants, set time ranges, and include extra meeting details in just a few steps. - Contact creation and management: Let the agent create new contacts or fetch existing ones, so scheduling is always quick and accurate. - Meeting details retrieval: Ask your agent to fetch specific meeting details or get a list of all meetings within a defined timeframe, keeping you up-to-date. - Access and manage calendar integrations: Direct your agent to list all connected calendars, add new integrations, or access available calendars for streamlined scheduling. - Template and meeting type discovery: Quickly retrieve available meeting templates and types, letting your agent optimize scheduling based on your preferences and routines. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `CALENDARHERO_ADD_CALENDAR_CONNECTION` | Add Calendar Connection | Add a new calendar directory/connection to the user's CalendarHero account. A directory is a calendar connection configuration that groups meeting types together. Use this to organize different types of meetings (e.g., sales calls, team meetings) under separate calendar connections. Returns the unique ID of the created directory. | | `CALENDARHERO_CREATE_CONTACT` | Create Contact | Creates a new contact in CalendarHero with the provided contact information. Returns the unique identifier of the created contact. | | `CALENDARHERO_CREATE_MEETING_REQUEST_V2` | Create Meeting Request V2 | Tool to create a new meeting request in CalendarHero. Use when scheduling a meeting with participants, time range, and additional details. | | `CALENDARHERO_CREATE_WEBHOOK` | Create Webhook | Creates or updates a webhook for a specific event type in CalendarHero. Use this to register a URL endpoint that will receive notifications when events occur (e.g., when a meeting request succeeds or a new contact is added). | | `CALENDARHERO_DELETE_CONTACT` | Delete Contact | Tool to delete a contact from CalendarHero by its unique identifier. Use when you need to permanently remove a contact from the system. | | `CALENDARHERO_DELETE_MEETING_TASK` | Delete Meeting Task | Tool to delete a meeting task/request from CalendarHero. Use when you need to remove a meeting task by its ID. | | `CALENDARHERO_DELETE_MEETING_TYPE` | Delete Meeting Type | Tool to delete a meeting type from the authenticated user's CalendarHero account. Use when you need to remove a meeting type configuration. Note: Cannot delete meeting types that have active or upcoming meetings scheduled. | | `CALENDARHERO_DELETE_USER_DIRECTORY` | Delete User Directory | Tool to delete a user directory by its UUID. Use when you need to remove a directory from the user's account. | | `CALENDARHERO_DELETE_WEBHOOK` | Delete Webhook | Tool to delete a webhook subscription for a specific event type. Use when you need to remove a webhook listener that was previously registered for CalendarHero events. | | `CALENDARHERO_FETCH_CONTACT` | Fetch Contact | Fetch Contact | | `CALENDARHERO_FETCH_MEETING_DETAILS` | Fetch Meeting Details | Tool to fetch details for meetings within a specified timeframe. Use this after user provides start and end datetimes in ISO8601. | | `CALENDARHERO_FETCH_USER_PROFILE` | Fetch User Profile | Tool to fetch the profile details of the authenticated user. Use after obtaining a valid access token. | | `CALENDARHERO_GET_ASSISTANT_MESSAGE` | Get Assistant Message | Tool to retrieve a reply message from the CalendarHero assistant. Use when you need to get an automated response or greeting from the assistant for the user. | | `CALENDARHERO_GET_CONTACT_COUNT` | Get Contact Count | Tool to get the total count of contacts in CalendarHero. Use when you need to know how many contacts exist. | | `CALENDARHERO_GET_MEETING_CATEGORIES` | Get Meeting Categories | Retrieves the user's meeting categories' stats for a specified time period. Use to analyze meeting distribution across different categories or types within a given month. | | `CALENDARHERO_GET_MEETING_TASKS` | Get Meeting Tasks | Retrieves the user's meeting requests/tasks from CalendarHero. Use when you need to check pending meeting requests, view scheduling tasks, or track meeting coordination progress. Supports filtering by state (active/upcoming/closed), pagination, and meeting type. | | `CALENDARHERO_GET_SEARCH_RESULT` | Get Search Result | Tool to get a search result by ID. Use when you have a search result ID from a previous /search request. | | `CALENDARHERO_GET_USER_DIRECTORY` | Get User Directory | Tool to retrieve a user's directory by its unique identifier. Use when you need to fetch configuration details for a specific directory including meeting types and tracking settings. | | `CALENDARHERO_GET_USER_ORGANIZATION` | Get User Organization | Tool to retrieve the authenticated user's organization details. Use when needing organization-level information. | | `CALENDARHERO_GET_USER_SAVINGS` | Get User Savings | Tool to retrieve the authenticated user's savings information from CalendarHero. Use to view time saved, efficiency metrics, or other savings data tracked by the platform. | | `CALENDARHERO_GET_WEBHOOK` | Get Webhook Configuration | Tool to get webhook configuration for a specific event type. Use when you need to check if a webhook is configured for meeting or contact events. | | `CALENDARHERO_GET_WEBHOOK_SAMPLE` | Get Webhook Sample | Tool to retrieve a sample webhook payload for a specific event type. Use when testing webhook integrations or understanding the structure of webhook data for different CalendarHero events. | | `CALENDARHERO_LIST_MEETING_TEMPLATES` | List Meeting Templates | Retrieves all meeting templates (reusable meeting configurations) for the authenticated user. Meeting templates contain pre-configured settings like duration, availability, video conferencing preferences, and custom options. Use this action to discover available templates before creating meetings or to understand a user's meeting type options. Returns an empty list if no templates have been created yet. | | `CALENDARHERO_LIST_MEETING_TYPES` | List Meeting Types | Retrieves all meeting types configured for the authenticated CalendarHero user. Meeting types are templates that define availability windows, durations, and booking URLs for different kinds of meetings (e.g., 'coffee', 'call', 'meeting'). Each meeting type has: - A unique identifier (e.g., 'coffee', 'call', 'meeting') - Availability windows (days and hours when meetings can be scheduled) - Booking URL for on-demand scheduling - Configuration for duration, timezone, notice period, etc. Use onlyTypes=true to get just the list of meeting type identifiers. Use onlyTypes=false (or omit) to get full configurations including all settings. This is a read-only operation that doesn't modify any data. | | `CALENDARHERO_LIST_USER_CALENDARS` | List User Calendars | Tool to list all calendar integrations connected to a user's CalendarHero account. Use after authenticating when you need to retrieve available calendars for scheduling. | | `CALENDARHERO_LIST_USER_DIRECTORIES` | List User Directories | Tool to retrieve all directories configured for a user. Use when you need to list available directories for scheduling or configuration purposes. | | `CALENDARHERO_SEARCH_CONTACT` | Search Contact | Tool to search for existing contacts. Use after confirming a need to find contacts by email or name. | | `CALENDARHERO_SEARCH_INTEGRATIONS` | Search Integrations | Tool to search across all user integrations for a query term. Use when you need to find events, meetings, or other data matching specific keywords across the user's connected calendar and productivity integrations. | | `CALENDARHERO_SEND_ASSISTANT_MESSAGE` | Send Assistant Message | Tool to send a user's message into the CalendarHero assistant. Use this to interact with the assistant using natural language for scheduling meetings, managing calendar events, or other calendar-related tasks. | | `CALENDARHERO_SEND_REMINDER` | Send Reminder | Sends an email reminder to all contacts/participants about a scheduled meeting request. Use this to notify attendees who need a reminder about an upcoming meeting. Requires the meeting task ID from a previously created meeting request. | | `CALENDARHERO_UPDATE_CONTACT` | Update Contact | Updates an existing contact in CalendarHero with new information. Use this action when you need to modify contact details such as name, email addresses, job title, organization, or phone numbers. Requires the contact's unique ID which can be obtained from CREATE_CONTACT or FETCH_CONTACT actions. Note: The 'email' field replaces ALL existing emails, so include all emails you want to keep. Use 'defaultEmail' to set the primary email for communications. Example usage: Update contact 507f1f77bcf86cd799439011 to change their email to 'newemail@example.com' and update their title to 'Senior Engineer'. | | `CALENDARHERO_UPDATE_MEETING_TYPES` | Update Meeting Types | Tool to update meeting type configurations for the authenticated CalendarHero user. Use when you need to modify existing meeting types' availability, durations, or settings. IMPORTANT: The meeting type name must already exist in the user's profile. To get existing meeting types, first use LIST_MEETING_TYPES action. This action updates properties like availability windows, notice periods, on-demand URLs, and other meeting-specific settings. Example: Update the 'coffee' meeting type to change the notice period from 4 hours to 5 hours, or modify the availability windows to only allow Monday-Wednesday bookings. | | `CALENDARHERO_UPDATE_RESTRICTED_APPS` | Update Restricted Apps | Tool to update the authenticated user's restricted apps settings. Use when you need to control which apps are restricted for the user. | | `CALENDARHERO_UPDATE_USER` | Update User | Tool to update the authenticated user's profile information. Use when you need to modify user details such as name, email, timezone, or preferences. | | `CALENDARHERO_UPDATE_USER_ADDRESS` | Update User Address | Tool to update the authenticated user's address settings by providing latitude and longitude coordinates. Use when the user needs to update their location for meeting scheduling or time zone detection. | | `CALENDARHERO_UPDATE_USER_DIRECTORY` | Update User Directory | Tool to update a user's directory in CalendarHero. Use when modifying directory settings such as title, meeting types, or configuration options. The directory UUID can be obtained from the user profile or directory listing endpoints. Ensure the directoryId in the request body matches the UUID path parameter. | | `CALENDARHERO_UPDATE_USER_INFO` | Update User Info | Updates the authenticated user's info settings in CalendarHero. Use this action when you need to modify user profile details such as name, language, timezone, contact information, or display preferences. Only the fields provided in the request will be updated; all other fields remain unchanged. This allows for partial updates without affecting other user settings. | | `CALENDARHERO_UPDATE_WORK_LOCATION` | Update Work Location | Tool to update the user's work location settings in CalendarHero. Use when the user needs to change their work location (e.g., 'Office', 'Home', 'Remote'). | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Calendarhero MCP server is an implementation of the Model Context Protocol that connects your AI agent to Calendarhero. It provides structured and secure access so your agent can perform Calendarhero 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 No description provided. ### 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 dependencies No description provided. ```python pip install composio-langchain langchain-mcp-adapters langchain python-dotenv ``` ```typescript npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters 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's API - COMPOSIO_USER_ID identifies the user for session management - OPENAI_API_KEY enables access to OpenAI's language models ```bash COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_composio_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import dependencies No description provided. ```python from langchain_mcp_adapters.client import MultiServerMCPClient from langchain.agents import create_agent from dotenv import load_dotenv from composio import Composio import asyncio import os load_dotenv() ``` ```typescript import { Composio } from '@composio/core'; import { LangchainProvider } from '@composio/langchain'; import { MultiServerMCPClient } from "@langchain/mcp-adapters"; import { createAgent } from "langchain"; import * as readline from 'readline'; import 'dotenv/config'; dotenv.config(); ``` ### 5. Initialize Composio client What's happening: - We're loading the COMPOSIO_API_KEY from environment variables and validating it exists - Creating a Composio instance that will manage our connection to Calendarhero tools - Validating that COMPOSIO_USER_ID is also set before proceeding ```python async def main(): composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) if not os.getenv("COMPOSIO_API_KEY"): raise ValueError("COMPOSIO_API_KEY is not set") if not os.getenv("COMPOSIO_USER_ID"): raise ValueError("COMPOSIO_USER_ID is not set") ``` ```typescript const composioApiKey = process.env.COMPOSIO_API_KEY; const userId = process.env.COMPOSIO_USER_ID; if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set'); if (!userId) throw new Error('COMPOSIO_USER_ID is not set'); async function main() { const composio = new Composio({ apiKey: composioApiKey as string, provider: new LangchainProvider() }); ``` ### 6. Create a Tool Router session What's happening: - We're creating a Tool Router session that gives your agent access to Calendarhero tools - The create method takes the user ID and specifies which toolkits should be available - The returned session.mcp.url is the MCP server URL that your agent will use - This approach allows the agent to dynamically load and use Calendarhero tools as needed ```python # Create Tool Router session for Calendarhero session = composio.create( user_id=os.getenv("COMPOSIO_USER_ID"), toolkits=['calendarhero'] ) url = session.mcp.url ``` ```typescript const session = await composio.create( userId as string, { toolkits: ['calendarhero'] } ); const url = session.mcp.url; ``` ### 7. Configure the agent with the MCP URL No description provided. ```python client = MultiServerMCPClient({ "calendarhero-agent": { "transport": "streamable_http", "url": session.mcp.url, "headers": { "x-api-key": os.getenv("COMPOSIO_API_KEY") } } }) tools = await client.get_tools() agent = create_agent("gpt-5", tools) ``` ```typescript const client = new MultiServerMCPClient({ "calendarhero-agent": { transport: "http", url: url, headers: { "x-api-key": process.env.COMPOSIO_API_KEY } } }); const tools = await client.getTools(); const agent = createAgent({ model: "gpt-5", tools }); ``` ### 8. Set up interactive chat interface No description provided. ```python conversation_history = [] print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Calendarhero related question or task to the agent.\n") while True: user_input = input("You: ").strip() if user_input.lower() in ['exit', 'quit', 'bye']: print("\nGoodbye!") break if not user_input: continue conversation_history.append({"role": "user", "content": user_input}) print("\nAgent is thinking...\n") response = await agent.ainvoke({"messages": conversation_history}) conversation_history = response['messages'] final_response = response['messages'][-1].content print(f"Agent: {final_response}\n") ``` ```typescript let conversationHistory: any[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log("Ask any Calendarhero related question or task to the agent.\n"); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: 'You: ' }); 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; } conversationHistory.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); const response = await agent.invoke({ messages: conversationHistory }); conversationHistory = response.messages; const finalResponse = response.messages[response.messages.length - 1]?.content; console.log(`Agent: ${finalResponse}\n`); rl.prompt(); }); rl.on('close', () => { console.log('\n👋 Session ended.'); process.exit(0); }); ``` ### 9. Run the application No description provided. ```python if __name__ == "__main__": asyncio.run(main()) ``` ```typescript main().catch((err) => { console.error('Fatal error:', err); process.exit(1); }); ``` ## Complete Code ```python from langchain_mcp_adapters.client import MultiServerMCPClient from langchain.agents import create_agent from dotenv import load_dotenv from composio import Composio import asyncio import os load_dotenv() async def main(): composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) if not os.getenv("COMPOSIO_API_KEY"): raise ValueError("COMPOSIO_API_KEY is not set") if not os.getenv("COMPOSIO_USER_ID"): raise ValueError("COMPOSIO_USER_ID is not set") session = composio.create( user_id=os.getenv("COMPOSIO_USER_ID"), toolkits=['calendarhero'] ) url = session.mcp.url client = MultiServerMCPClient({ "calendarhero-agent": { "transport": "streamable_http", "url": url, "headers": { "x-api-key": os.getenv("COMPOSIO_API_KEY") } } }) tools = await client.get_tools() agent = create_agent("gpt-5", tools) conversation_history = [] print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Calendarhero related question or task to the agent.\n") while True: user_input = input("You: ").strip() if user_input.lower() in ['exit', 'quit', 'bye']: print("\nGoodbye!") break if not user_input: continue conversation_history.append({"role": "user", "content": user_input}) print("\nAgent is thinking...\n") response = await agent.ainvoke({"messages": conversation_history}) conversation_history = response['messages'] final_response = response['messages'][-1].content print(f"Agent: {final_response}\n") if __name__ == "__main__": asyncio.run(main()) ``` ```typescript import { Composio } from '@composio/core'; import { LangchainProvider } from '@composio/langchain'; import { MultiServerMCPClient } from "@langchain/mcp-adapters"; import { createAgent } from "langchain"; import * as readline from 'readline'; import 'dotenv/config'; const composioApiKey = process.env.COMPOSIO_API_KEY; const userId = process.env.COMPOSIO_USER_ID; if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set'); if (!userId) throw new Error('COMPOSIO_USER_ID is not set'); async function main() { const composio = new Composio({ apiKey: composioApiKey as string, provider: new LangchainProvider() }); const session = await composio.create( userId as string, { toolkits: ['calendarhero'] } ); const url = session.mcp.url; const client = new MultiServerMCPClient({ "calendarhero-agent": { transport: "http", url: url, headers: { "x-api-key": process.env.COMPOSIO_API_KEY } } }); const tools = await client.getTools(); const agent = createAgent({ model: "gpt-5", tools }); let conversationHistory: any[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log("Ask any Calendarhero related question or task to the agent.\n"); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: 'You: ' }); 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; } conversationHistory.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); const response = await agent.invoke({ messages: conversationHistory }); conversationHistory = response.messages; const finalResponse = response.messages[response.messages.length - 1]?.content; console.log(`Agent: ${finalResponse}\n`); rl.prompt(); }); rl.on('close', () => { console.log('\nSession ended.'); process.exit(0); }); } main().catch((err) => { console.error('Fatal error:', err); process.exit(1); }); ``` ## Conclusion You've successfully built a LangChain agent that can interact with Calendarhero through Composio's Tool Router. Key features of this implementation: - Dynamic tool loading through Composio's Tool Router - Conversation history maintenance for context-aware responses - Async Python provides clean, efficient execution of agent workflows You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Calendarhero MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/calendarhero/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/calendarhero/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/calendarhero/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/calendarhero/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/calendarhero/framework/codex) - [OpenClaw](https://composio.dev/toolkits/calendarhero/framework/openclaw) - [Hermes](https://composio.dev/toolkits/calendarhero/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/calendarhero/framework/cli) - [Google ADK](https://composio.dev/toolkits/calendarhero/framework/google-adk) - [Vercel AI SDK](https://composio.dev/toolkits/calendarhero/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/calendarhero/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/calendarhero/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/calendarhero/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. - [Calendly](https://composio.dev/toolkits/calendly) - Calendly is an appointment scheduling tool that automates meeting invitations, availability checks, and reminders. It helps individuals and teams avoid endless email back-and-forth when booking meetings. - [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 Calendarhero MCP? With a standalone Calendarhero MCP server, the agents and LLMs can only access a fixed set of Calendarhero tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Calendarhero and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with LangChain? Yes, you can. LangChain 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 Calendarhero tools. ### Can I manage the permissions and scopes for Calendarhero while using Tool Router? Yes, absolutely. You can configure which Calendarhero 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 Calendarhero data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)