Calendly MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level: DEBUG, INFO, WARNING, ERROR (default: INFO) | |
| LICENSE_KEY | No | Lemon Squeezy premium license key | |
| CALENDLY_BASE_URL | No | Override the Calendly API base URL (for testing) | |
| CALENDLY_ACCESS_TOKEN | Yes | Calendly Personal Access Token or OAuth2 token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_upcoming_eventsB | List upcoming scheduled Calendly events. Returns event name, time, invitees, location, and status. |
| get_event_detailsA | Get full details of a specific Calendly event including invitees, location, conferencing details, and cancellation info. |
| search_eventsB | Search Calendly events by invitee name or email address. Performs a case-insensitive partial match. |
| check_availabilityC | Check available time slots from your Calendly availability schedules and show busy periods for a date range. |
| get_busy_timesB | Get busy/unavailable time periods for a date range. Shows all times when you are not available for meetings. |
| list_event_typesA | List all configured Calendly event types with name, duration, slug, and availability status. |
| get_event_type_detailsA | Get detailed configuration of a specific Calendly event type including description, booking URL, custom questions, and visibility. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clear, distinct purpose: availability checking vs. busy times, event details vs. event type details, listing vs. searching. No two tools could be easily confused.
All tools follow a consistent verb_noun pattern in snake_case (check_availability, get_busy_times, list_event_types, etc.), making the tool surface predictable and easy to navigate.
Seven tools cover the core Calendly interactions (listing, searching, details, availability) without redundancy. The number is well-scoped for a focused MCP server.
The set lacks create, update, or delete operations for events or event types, which are common needs. It is read-only and search-focused, leaving significant lifecycle gaps for many use cases.