The Cal.com Calendar MCP Server provides appointment scheduling capabilities through the Cal.com Calendar API, allowing you to add, update, delete, and list calendar appointments programmatically.
Before using the MCP server, you'll need a Cal.com API key:
You can run the Cal.com Calendar MCP server using either Docker or NPX.
Add the following configuration to your claude_desktop_config.json
:
{
"mcpServers": {
"calcom-calendar": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"CALCOM_API_KEY",
"mcp/calcom-calendar"
],
"env": {
"CALCOM_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
To build the Docker image:
docker build -t mcp/calcom-calendar:latest -f Dockerfile .
Alternatively, add this configuration to your claude_desktop_config.json
to use NPX:
{
"mcpServers": {
"calcom-calendar": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-calcom-calendar"
],
"env": {
"CALCOM_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
The Cal.com Calendar MCP server provides four main tools:
Use calcom_add_appointment
to schedule new calendar appointments:
Required inputs:
eventTypeId
(number): The Cal.com event type IDstartTime
(string): Start time in ISO format (YYYY-MM-DDTHH:mm:ss.sssZ)endTime
(string): End time in ISO format (YYYY-MM-DDTHH:mm:ss.sssZ)name
(string): Attendee's nameemail
(string): Attendee's emailnotes
(string, optional): Additional notes for the appointmentUse calcom_update_appointment
to modify existing appointments:
Required inputs:
bookingId
(number): The Cal.com booking ID to updateOptional inputs:
startTime
(string): New start time in ISO formatendTime
(string): New end time in ISO formatnotes
(string): New notes for the appointmentUse calcom_delete_appointment
to cancel and remove appointments:
Required inputs:
bookingId
(number): The Cal.com booking ID to deleteOptional inputs:
reason
(string): Reason for cancellationUse calcom_list_appointments
to view scheduled appointments:
Required inputs:
startDate
(string): Start date in YYYY-MM-DD formatendDate
(string): End date in YYYY-MM-DD formatThere are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.