Cal.com
Connect Cal.com to create, reschedule, and cancel bookings, and manage event types, availability, and connected calendars.
One Cal.com API key, starting with cal_ or cal_live_, that you paste into PopMCP's API Key field.
- Setup time
- 3 min
- Auth
- API credentials
- API base URL
- https://api.cal.com/v2
- Rate limits
- 120 requests per minute per API key. Cal.com will raise it to 200 on request, and higher with a paid arrangement.
Before you begin
- A Cal.com cloud account at app.cal.com. The free plan is enough
- The key inherits your own permissions, so create it as a user who can see every event type, booking and team you want PopMCP to reach
- Self-hosted Cal.com works too, but the key must come from your own instance and the API host will differ
Get your credentials
Open Settings, then Developer
Click the dropdown beside your name and choose My Settings. Scroll the settings sidebar to the Developer section and click API keys.
Developer
Webhooks, API keys and OAuth clients for this account.
Developer sits below My account, Security and Billing in the settings sidebar.
Add a key
Click + Add in the upper-right corner of the API keys page.
API keys
API keys allow other apps to communicate with Cal.com.
| Name | API key | Status | Expires |
|---|---|---|---|
| ZapierCreated Mar 4, 2026 | cal_live_****91be | Active | Never |
| Booking widgetCreated Nov 18, 2025 | cal_live_****0c14 | Expired | Jun 1, 2026 |
There is no limit on the number of active API keys.
Name it and turn on Never expires
Enter PopMCP as the Personal note and switch on Never expires. Click Save.
API keys
API keys allow other apps to communicate with Cal.com.
With Never expires off, the key stops working on the chosen date.
Copy the key into PopMCP
Copy the key from the dialog before you close it. Paste it into PopMCP's API Key field with the cal_live_ prefix intact, then save.
API keys
API keys allow other apps to communicate with Cal.com.
Lost it? Delete the key and add a new one.
Connect in PopMCP
Open your workspace, choose Cal.com in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API Keysecret | In Cal.com go to Settings → Developer → API Keys and create an API key (it starts with cal_ or cal_live_; older docs call this the Security tab). Copy it exactly. It's sent as an Authorization: Bearer header, stored encrypted, and used server-side only.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Cal.com immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
The Cal.com connector in PopMCP shows Connected. Asking for your event types returns the same list you see under Event Types in app.cal.com.
Troubleshooting
401 Unauthorized
Why: The key was deleted, has expired, or the cal_live_ prefix was trimmed when pasting.
Fix: Add a fresh key with Never expires on and paste the whole string, prefix included.
403 Forbidden on team endpoints
Why: The key inherits the creator's permissions and that user is not on the team.
Fix: Mint the key from an account that is a member of the team, or grant that user access in Cal.com.
429 Too Many Requests
Why: You exceeded 120 requests per minute on this key.
Fix: Space the calls out, or ask Cal.com to raise the limit for your key.
Calls hit the v1 API instead of v2
Why: Older Cal.com integrations pass the key as an ?apiKey= query parameter against api.cal.com/v1.
Fix: PopMCP uses v2 with an Authorization: Bearer header. Make sure you pasted a key rather than a v1 URL.