A
licenseA
qualityD
maintenanceMCP server that connects AI agents to calendars, bookings, and scheduling polls via the Model Context Protocol.
22
4 npm
MIT
Calendly MCP Server
by 84emllc
Related Servers
Alternatives to Calendly MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA Model Context Protocol server that integrates Google Calendar with Claude Desktop, enabling users to manage calendar events (view, create, update, delete) through natural language.589 npm59MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server that allows Claude and other MCP clients to interact with Google Calendar. This server enables AI assistants to manage your calendar events, check availability, and handle scheduling tasks.MIT
- AlicenseAqualityDmaintenanceAn MCP server that connects Claude Desktop and Claude Code to your Calendly account, enabling natural-language scheduling management.7MIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing a standardized interface for interacting with Calendly's scheduling and event management tools.6MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for Google Calendar integration, enabling AI assistants to manage events, check availability, and work with multiple accounts and calendars.97 npmMIT
TDQS
A3.6/5.0
Scored across 12 tools
Disambiguation5/5
Each tool targets a distinct resource and action: authentication (refresh_access_token, get_oauth_url, exchange_code_for_tokens), user info (get_current_user), events (list_events, get_event, cancel_event, schedule_event), invitees (list_event_invitees), organization (list_organization_memberships), event types (list_event_types), and availability (get_event_type_availability). No ambiguity between list_events and get_event; they clearly differ in scope.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in lowercase snake_case (e.g., list_events, get_event, cancel_event, schedule_event). Verbs are specific and non-repetitive across different resources, and no mixed naming conventions are present.
Tool Count5/5
With 12 tools, the server is well-scoped for a Calendly integration. It covers authentication, user, events, invitees, organization memberships, event types, availability, and scheduling without feeling bloated or sparse.
Completeness4/5
Core workflows are covered: OAuth authentication, viewing user info, listing and getting events, listing invitees, cancelling events, listing event types, fetching availability, and scheduling. Minor gaps exist such as creating/updating event types or rescheduling events, but these are not critical for the primary scheduling use case.
Maintenance
ActivityInactive
ResponsivenessNo issues