Skip to content
Docs

Cal.com

Scheduling guidance and agent guardrails.

1

Cal.com is guidance-only by default; the core does not ship Cal.com UI, OAuth routes, token storage, or account configuration by default.

2

Agents should read current Cal.com docs before changing event types, slots, bookings, schedules, webhooks, embeds, Atoms, MCP instructions, or API usage.

3

Use the official Cal.com CLI first. If the CLI is missing or unauthenticated, guide the user through install/auth setup before using direct API calls.

4

Prefer the hosted MCP server at https://mcp.cal.com/mcp when the user's MCP client supports OAuth.

5

Use direct API calls only as an explicit fallback when CLI/MCP is unavailable or insufficient, and document why.

6

Keep Cal.com payments disabled in product code; Polar remains the only billing provider.