Docs

Cal.com

Internal consulting scheduling, Pro-only scheduling guidance, and Cal.com agent guardrails.

1

Cal.com is used for scheduling. Polar remains the payment source of truth for paid products and consulting services.

2

Internal VibeShip consulting links use CAL_API_KEY for setup scripts plus VIBESHIP_CAL_USERNAME and VIBESHIP_CAL_BOOKING_LINKS for runtime links.

3

Run pnpm cal:doctor -- --json before declaring booking links ready; pnpm cal:sync is CLI-first and direct API fallback requires --api-fallback.

4

Generated Pro repos include Cal.com CLI/MCP-first scheduling guidance for agents; generated Core repos must not include Cal.com routes, OAuth env, token-vault helpers, settings UI, or Cal docs.

5

Use the official Cal.com CLI first, guide users through CLI install/auth when needed, and prefer hosted MCP where supported.

6

Check current official docs at cal.com/docs/llms.txt before changing event types, bookings, slots, webhooks, embeds, Atoms, or MCP guidance.

7

For agent-operated scheduling, prefer Cal.com's hosted MCP server at https://mcp.cal.com/mcp when the user's MCP client supports OAuth.