Cal.com Calendar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CALCOM_API_KEY | Yes | Your Cal.com API key generated from Settings > Developer > API Keys |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calcom_add_appointmentA | Creates a new appointment in Cal.com calendar. Use this for scheduling new meetings or appointments. Requires event type ID, start time, end time, name, email, and optional notes. |
| calcom_update_appointmentB | Updates an existing appointment in Cal.com calendar. Use this for rescheduling or modifying existing appointments. Requires booking ID and the fields to update. |
| calcom_delete_appointmentA | Deletes an existing appointment from Cal.com calendar. Use this for canceling appointments. Requires booking ID. |
| calcom_list_appointmentsB | Lists appointments from Cal.com calendar. Can be filtered by date range. Returns a list of appointments with their details. |
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 4 tools
Each tool has a clearly distinct purpose targeting specific CRUD operations for appointments: add (create), delete (remove), list (read), and update (modify). There is no overlap in functionality, making it easy for an agent to select the correct tool based on the intended action.
All tool names follow a consistent pattern: 'calcom_' prefix followed by a verb_noun structure (add_appointment, delete_appointment, list_appointments, update_appointment). This uniformity enhances predictability and readability across the toolset.
With 4 tools, the server is well-scoped for managing appointments in a calendar system. Each tool serves a distinct and essential function (create, read, update, delete), providing a complete set without unnecessary bloat or gaps for this domain.
The toolset offers complete CRUD coverage for appointments: create (add), read (list), update, and delete. This covers the full lifecycle of appointment management in Cal.com, with no obvious gaps that would hinder an agent from performing typical scheduling tasks.