scheduling
Cal.com MCP Gateway for AI Agents
Expose Cal.com tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.
6 functions 5 read 1 write Bearer token auth
Cal.com MCP Gateway
Expose Cal.com to MCP clients with `kosmokrator mcp:serve --integration=cal`.
If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server. The gateway exposes only the selected integration in the example below.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash kosmokrator mcp:gateway:install --integration=cal --write=deny --json {
"mcpServers": {
"kosmokrator-cal": {
"type": "stdio",
"command": "kosmo",
"args": [
"mcp:serve",
"--integration=cal",
"--write=deny"
]
}
}
} Serve Manually
kosmokrator mcp:serve --integration=cal --write=deny MCP Tool Names
KosmoKrator exposes integration tools through the gateway with stable names:
| MCP tool | Source function | Type |
|---|---|---|
integration__cal__cal_list_event_types | cal.cal_list_event_types | Read read |
integration__cal__cal_get_event_type | cal.cal_get_event_type | Read read |
integration__cal__cal_list_bookings | cal.cal_list_bookings | Read read |
integration__cal__cal_get_booking | cal.cal_get_booking | Read read |
integration__cal__cal_create_booking | cal.cal_create_booking | Write write |
integration__cal__cal_get_current_user | cal.cal_get_current_user | Read read |
Write Access
Start with --write=deny for read-only MCP clients. Use --write=ask or
--write=allow only when the client and workspace are trusted.