# Cal.com

> Open-source scheduling — booking pages, availability, and event types for AI agents.

[Canonical HTML page](https://top-mcps.com/mcp/cal-com) · [server.json](https://top-mcps.com/mcp/cal-com.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "cal-com": {
      "command": "npx",
      "args": [
        "-y",
        "@calcom/mcp"
      ],
      "env": {
        "CAL_API_KEY": "${CAL_API_KEY}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export CAL_API_KEY=YOUR_API_KEY
claude mcp add cal-com -- npx -y @calcom/mcp
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "cal-com": {
      "command": "npx",
      "args": [
        "-y",
        "@calcom/mcp"
      ],
      "env": {
        "CAL_API_KEY": "${CAL_API_KEY}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "cal-com": {
      "command": "npx",
      "args": [
        "-y",
        "@calcom/mcp"
      ],
      "env": {
        "CAL_API_KEY": "${CAL_API_KEY}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "cal-com": {
      "command": "npx",
      "args": [
        "-y",
        "@calcom/mcp"
      ],
      "env": {
        "CAL_API_KEY": "${CAL_API_KEY}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "cal-com": {
      "command": "npx",
      "args": [
        "-y",
        "@calcom/mcp"
      ],
      "env": {
        "CAL_API_KEY": "${CAL_API_KEY}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@calcom/mcp"
          ],
          "env": {
            "CAL_API_KEY": "${CAL_API_KEY}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.cal-com]
command = "npx"
args = [
  "-y",
  "@calcom/mcp",
]
env = { CAL_API_KEY = "${CAL_API_KEY}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "cal-com": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@calcom/mcp"
        ]
      },
      "env": {
        "CAL_API_KEY": "${CAL_API_KEY}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Apps directory`

Cal.com doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

```none

```

## At a glance

- **Maintainer:** Cal.com
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** CAL_API_KEY
- **Supported clients:** Claude, Cursor, Any MCP-compatible client
- **License:** AGPL-3.0
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-05-26
- **GitHub stars:** 22 (fetched 2026-05-26T10:50:23.360Z)
- **Score:** 54/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/calcom/cal-mcp

## Security & scope

- **Access scope:** read-write
- **Sandbox:** API key grants account-wide access to bookings and availability.
- **Gotchas:**
  - AGPL license affects derivative SaaS uses.
  - Public booking links expose availability — review which event types are public.

## Quick answer

**What it does.** Provides MCP tools for listing event types, fetching availability, creating and updating bookings, and managing user schedules against a Cal.com account.

**Best for:**
- External booking links
- Self-hosted scheduling
- Multi-step booking flows
- Team-based round-robin scheduling

**Not for:**
- Internal-only calendar access
- Single-user personal scheduling

## Description

The Cal.com MCP exposes Cal.com's booking, availability, and event-type APIs. Self-host the booking platform or use the SaaS, then let an agent share booking links, query availability, or create one-off events without leaving the conversation.

## Why it matters

External scheduling is the most common assistant request after email triage. Cal.com is the leading open-source alternative to Calendly with a real API and self-host story.

## Key features

- Public booking pages
- Event types and availability
- Team round-robin
- Self-host or managed
- Webhook integrations

## FAQ

### Do I need a Cal.com account?

Yes — the MCP requires a Cal.com API key from either the SaaS at cal.com or a self-hosted instance. Free plan works for personal use.

### Can the agent create a booking on someone's behalf?

It can create a booking against an event type that allows it, but most external flows still send a public link and let the invitee book themselves. The MCP supports both.

### How is it different from Calendly?

Functionally similar; the differentiator is the open-source license and self-host option. If you have compliance constraints that block sending availability to a US SaaS, Cal.com is the safer pick.

## Changelog

- **2026-05-26** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-01-20** — Initial directory listing.