Calendly MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CALENDLY_API_KEY | No | Personal Access Token for Calendly API (alternative to OAuth) | |
| CALENDLY_USER_URI | No | User URI for automatic defaults | |
| CALENDLY_CLIENT_ID | No | OAuth 2.0 client ID (required if not using PAT) | |
| CALENDLY_ACCESS_TOKEN | No | OAuth access token (optional, if already obtained) | |
| CALENDLY_CLIENT_SECRET | No | OAuth 2.0 client secret (required if not using PAT) | |
| CALENDLY_REFRESH_TOKEN | No | OAuth refresh token (optional) | |
| CALENDLY_ORGANIZATION_URI | No | Organization URI for automatic defaults |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_oauth_urlA | Generate OAuth authorization URL for user authentication |
| exchange_code_for_tokensA | Exchange authorization code for access and refresh tokens |
| refresh_access_tokenC | Refresh access token using refresh token |
| get_current_userA | Get the current authenticated user information |
| list_eventsC | List scheduled events for the authenticated user |
| get_eventB | Get details of a specific event |
| list_event_inviteesB | List invitees for a specific event |
| cancel_eventC | Cancel a specific event |
| list_organization_membershipsB | List organization memberships for the authenticated user |
| list_event_typesB | List available event types for scheduling meetings |
| get_event_type_availabilityB | Get available time slots for a specific event type |
| schedule_eventB | Schedule a meeting by creating an invitee for a specific event type and time |
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 12 tools
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.
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.
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.
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.