Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.
Cal.Com MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Cal.Com MCP directly instead of describing what you should do. Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.
Cal.com Companion lets you manage your Cal.com schedule from anywhere. It ships as a mobile app (iOS & Android), a set of browser extensions (Chrome, Firefox, Safari, Edge), and home-screen widgets — all from a single codebase.
Once Cal.Com MCP is connected, these are the calls the assistant has available:
Prerequisites — The Prerequisites tool exposed by this serverEnvironment — Copy the example env file and fill in your Cal.com OAuth credentials:@calcom/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: TELEGRAM_BOT_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cal.Com MCP's toolset — Prerequisites, Environment — is a fair guide to whether it matches your workflow.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Environment | Copy the example env file and fill in your Cal.com OAuth credentials: |
{
"mcpServers": {
"calcom": {
"command": "npx",
"args": ["-y", "@calcom/cli"],
"env": {
"TELEGRAM_BOT_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| TELEGRAM_BOT_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.