A
licenseA
qualityD
maintenanceMCP server for the Cal.com API v2, providing 24 tools for managing bookings, event types, availability slots, schedules, calendars, user profile, and out-of-office entries.
24
12
1
MIT
booking_chest
by dsddet
Related Servers
Alternatives to booking_chest
No user-submitted related servers found.
Related Servers
- PythonMIT
- FlicenseNot gradedqualityDmaintenanceExposes Cal.com scheduling tools to AI agents via MCP, enabling listing event types, checking availability, and managing bookings (create, cancel, reschedule).-
- AlicenseAqualityBmaintenanceAgent-native MCP server for Carly, the AI scheduling assistant. Exposes 11 tools to read and manage booking pages, event types, calendars, bookings, and available slots. Allows you to manage and create booking pages from the command line.135MIT
- AlicenseNot gradedqualityCmaintenanceThis MCP server enables Claude to read and manage self-hosted CalDAV calendars (SOGo, Nextcloud, Radicale, etc.) with strict safety guardrails: read-only by default, optional writes only when explicitly enabled, no permanent deletes, and no event invitations.MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for the Calendly API. Manage events, invitees, and schedule meetings directly via AI assistants.1274MIT
TDQS
B3/5.0
Scored across 68 tools
Disambiguation4/5
Most tools target a distinct resource and action, and the descriptions clarify potential overlaps like reserve_slot vs create_booking or the various webhook scopes. However, with 68 tools, there are enough similar list/get/create/update/delete patterns (especially around webhooks and calendars) that an agent may occasionally need to read descriptions carefully.
Naming Consistency4/5
The toolset predominantly follows a get/list/create/update/delete + resource pattern, with slight deviations like refresh_api_key, set_destination_calendar, check_ics_feed, and add_selected_calendar. These deviations are still readable and mostly action-first, so the naming is fairly consistent overall.
Tool Count1/5
68 tools is an extremely large surface for a single MCP server, well beyond the 50+ threshold for a low score. While the domain is broad, the sheer number will likely overwhelm agents and increase the chance of selecting an irrelevant tool.
Completeness4/5
The toolset covers most core booking workflows: schedules, event types, availability, bookings, calendars, webhooks, and team management. Minor gaps exist, such as no get_event_type_webhook for non-team event types, no delete/removal for ICS feeds, and limited team booking detail operations, but agents can generally complete end-to-end tasks.
Maintenance
ActivityInactive
ResponsivenessSyncing