Cal.com MCP server
Find meeting types and existing bookings before an agent helps coordinate the next appointment. Access is gated: request enablement for your organization before connecting.
Agent workflows for Cal.com.
List event types
Use when choosing one of the connected user’s meeting types before checking availability. Returns event IDs, titles, slugs, durations and schedule IDs. Lists the authenticated user’s types without a public username search.
List bookings
Use when checking booked meetings or locating a booking before changing it. Filter by attendeeEmail, eventTypeId, bookingUid or time range; pass pagination.nextCursor as cursor to continue.
Get booking
Use when inspecting an account-listed booking or reconciling an unknown write before retrying. Checks account visibility before fetching personal details; unlisted and series UIDs return not_found. Visibility includes attendee bookings and members’ bookings for team/org admins.
7 Cal.com actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
5Look things up, subject to your permissions.
- cal_com.list_event_typesList event types
Use when choosing one of the connected user’s meeting types before checking availability. Returns event IDs, titles, slugs, durations and schedule IDs. Lists the authenticated user’s types without a public username search.
- cal_com.list_bookingsList bookings
Use when checking booked meetings or locating a booking before changing it. Filter by attendeeEmail, eventTypeId, bookingUid or time range; pass pagination.nextCursor as cursor to continue.
- cal_com.get_bookingGet booking
Use when inspecting an account-listed booking or reconciling an unknown write before retrying. Checks account visibility before fetching personal details; unlisted and series UIDs return not_found. Visibility includes attendee bookings and members’ bookings for team/org admins.
- cal_com.list_schedulesList schedules
Use when inspecting the connected user’s working hours, timezone and date overrides. These are availability rules; use get_available_slots to account for existing calendar conflicts.
- cal_com.get_available_slotsGet available slots
Use when checking free times with a connected API key. Supply a UTC interval of at most 31 days; bookingUidToReschedule excludes that booking from busy-time checks. An empty result means no availability.
write
1Create and change things. Allow, or ask the user first.
- cal_com.reschedule_bookingReschedule booking
Use when moving an approved booking, not proposing. Account includes attendee bookings and members’ bookings for team/org admins. New UID; old cancelled. Hosts/attendees may get notices and see reasons. Unknown may mean pre-check failed; read back via get_booking before retrying.
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- cal_com.cancel_bookingCancel booking
Use when cancelling an approved single booking, not tentative/series changes. Account includes attendee bookings and members’ bookings for team/org admins. Hosts/attendees may get notices and see reasons. Unknown may mean pre-check failed; read back via get_booking before retrying.
Control access to Cal.com.
After early access is enabled, connect the intended Cal.com account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- cal_com.reschedule_booking: require approval
- cal_com.cancel_booking: deny
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Cal.com connects.
Connect Cal.com using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Cal.com with your AI client.
Request access to Cal.com first. An Arc0 administrator must enable it for your organization before these actions appear. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Cal.com with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpCal.com with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpCal.com with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpCal.com with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpCal.com with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpCal.com with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
Cal.com and Arc0, answered.
Does Cal.com work with Claude Desktop and Claude Code?
Yes, after early access is enabled for your organization and you connect the intended account. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.
Can I use Cal.com with OpenAI Codex, ChatGPT and Cursor?
Yes, after early access is enabled for your organization and you connect the intended account. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.
Is this the official Cal.com MCP server?
This is Arc0’s integration page, not a claim of an official Cal.com server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Cal.com for its own current MCP offerings.
Which Cal.com actions are supported?
7 registry-defined actions: 5 read, 1 write and 1 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.
Which permissions does Cal.com need?
Connect Cal.com using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
Can I restrict writes in Cal.com?
You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.
What does Cal.com through Arc0 cost?
See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.
Request Cal.com access.
Cal.com MCP server: 7 actions including list event types, list bookings, get booking. Request early access through Arc0.
Free to build · MCP + REST · Audit log on every plan
Cal.com and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Cal.com.