Cal.com AI and MCP: Cal.ai Phone Agent, MCP Server and Agents

What Cal.com AI actually means in 2026

Search for Cal.com AI and you get four different things under one name. Cal.ai is a voice agent that phones your attendees from inside a workflow. The MCP server lets assistants such as Claude, Cursor and VS Code read and change your Cal.com account. Cal.com Agents let you run your agenda from Slack, Telegram, email or a command line. And smaller AI features sit inside the product itself: an assistant that drafts routing forms and Notes, which summarizes recorded calls. Each has its own price logic, its own plan rules and its own maturity.

This guide takes them one at a time, then closes with four setups we think are worth copying. We read the help center, the developer docs, the release notes, the privacy policy and the terms. One warning first. The names have moved around a lot, and older blog posts describe products that no longer work the way they say. Where pages disagree, we follow the newest one. The short version: the phone agent is the paid, metered piece, while the MCP server and Agents cost nothing extra beyond your plan.

Cal.ai: a phone agent that lives inside workflows

Cal.ai is not a separate app you open. It is a workflow action called Call attendee using Cal.ai Voice Agent, sitting next to the email, SMS and WhatsApp actions you already know. Through phone calls it can confirm, book, reschedule, cancel and follow up on meetings, around the clock ^[1]. You shape what it says with an initial message and a general prompt, and you can drop variables into the prompt so each call carries the right name, time and event. Since the October 2025 release you can also change the agent's voice and language, and inbound calls were added.

The events that start a call

Because Cal.ai rides on workflows, the triggers are the workflow triggers: before an event starts, when a booking is made, cancelled or rescheduled, after an event ends, when a booking is requested or rejected, when a payment starts or succeeds, and when a no-show is updated. Since November 2025 a routing form submission can also fire the call, including a submission that ended without a booking. That last trigger is the most interesting one for sales teams, and we come back to it in the playbook.

What happens when nobody picks up

Missed calls are handled by the workflow, not by you. Depending on your settings, Cal.ai can leave a voicemail, send a follow-up message or try again later. The dashboard shows call transcripts, completion and booking rates, and a sentiment reading of how each conversation went. That gives a manager something to review beyond a call count. Cal.com also argues that a voice agent helps clients who struggle with web forms, naming seniors and people with disabilities. That is a fair point for clinics and service businesses whose clients do not live in their inbox.

What a Cal.ai call costs

Cal.ai is paid for in credits, the same currency that funds SMS and WhatsApp. One credit is one cent, and a call costs 29 credits a minute, or $0.29 ^[2]. Test calls from the web count too, so budget a few dollars for tuning the prompt. Teams includes 750 credits per member a month, Organizations 1,000, and Enterprise gets unlimited credits. Free accounts get none but can buy them. Credits renew every month.

Here is what that buys, by our arithmetic. A Teams seat's 750 credits cover about 25 minutes of calling a month, and an Organizations seat about 34 minutes. A three-minute confirmation call uses 87 credits, or $0.87. So a practice making 200 such calls a month would spend $174 on calls alone. Those included credits disappear quickly once calls go out daily, and the SMS reminders you keep running draw from the same pool.

Phone numbers and the 11 countries

Cal.com sells only US phone numbers for the agent, at $5 a month each. Anywhere else, you import a Twilio number through Elastic SIP trunking. Calls can reach 11 countries: the US, Canada, the UK, Australia, Germany, France, Spain, Italy, Mexico, Japan and India. On a team workflow, only team admins or owners can buy, import, change or remove a number. One technical note for importers: since September 30, 2026 the SIP trunk has to point at a Retell AI address, because the older LiveKit-hosted one was retired.

Which plan it really needs

The Cal.ai page says the agent is available on all plans. The help center adds a qualification: Free accounts are limited to the default reminder email and cannot build custom workflows. Since Cal.ai is a workflow action with no included credits on Free, the honest reading is that Teams is where it starts to make sense. Our Cal.com review covers what else that plan adds.

From email assistant to phone agent, and back again

Cal.ai has changed shape three times. It launched in 2023 as an email assistant: you wrote to your own address at cal.ai and it found slots, cancelled or rescheduled for you. The blog post that promoted it in March 2024 now carries a maintenance notice. By February 2025 Cal.com had retired the email assistant and relaunched Cal.ai as a voice agent, promising further changes during the year. The voice agent is what the help center describes today.

Then came a twist. The September 2026 release put Cal.ai back in the app store as a calendar agent. You type an event title such as @cal book followed by a name in your own calendar, and it books the meeting without you leaving the calendar. So the name now covers two products. The app store listing still describes an email-style assistant, while the FAQ and the AI page describe the phone agent. When a colleague says we use Cal.ai, ask which one. Both share the name, and neither should be confused with the third-party voice agents Cal.com also lists, such as Retell AI, Synthflow and ElevenLabs.

The MCP server: Cal.com inside Claude, Cursor and VS Code

The Model Context Protocol server wraps API v2 so that an AI assistant can manage bookings, event types and schedules in plain language. Cal.com names Claude Desktop, Cursor and VS Code among the supported clients. Ask what do I have on Thursday or move my 3 pm to Friday, and the assistant calls the right endpoint instead of you clicking through settings.

Hosted or local

The hosted server is the easy route. It runs at mcp.cal.com, speaks Streamable HTTP and signs you in with OAuth 2.1, so you never paste an API key ^[3]. In Claude you add the address mcp.cal.com/mcp as a custom connector, approve access, and you are done. The local route runs the npm package @calcom/cal-mcp through npx over stdio, with your API key in a CAL_API_KEY environment variable and Node.js 18 or later installed. Pick local when you want the key and the process on your own machine, or when you script against a self-managed setup. Both routes reach the same API.

What it can do, and how to narrow it

The tools cover your profile, event types, bookings, schedules, availability, conferencing, routing forms and organizations. Booking tools can confirm pending bookings, mark absences and manage attendees. Event type tools show change history and CRM sync errors. Three catalog tools let a client search, describe and run any API v2 operation, which is how the server reaches endpoints that lack a dedicated tool. The help center lists 34 tools and the developer docs list 70, so expect the count to keep moving. You can limit a session to chosen toolsets with a query parameter on the server address. Do that. An assistant that can only read bookings cannot cancel one by mistake.

Cal.com Agents: Slack, Telegram, email and the CLI

Cal.com Agents arrived in the March 2026 release. They let you check and change your agenda from Slack, Telegram, email or a new command-line tool, so the scheduler comes to the chat you already live in. The same launch shipped skills for builders who connect hosted agents to the Cal.com API, including one for OpenClaw. For anyone building their own agent, the developer guide is direct: if your agent can run commands, use the official CLI, published as @calcom/cli, rather than calling the API by hand.

The guide also lists rules your agent has to respect. Every API v2 call needs the cal-api-version header, or it fails with a 404. The booking endpoint is public, so an agent can book for outside guests without their credentials. An instant flag can ring available team members at once, if the event type allows instant meetings. Agents running on the platform API spend credits, logged as their own usage type. And booking pages now expose small WebMCP tools that browser agents can use to read event details and open times without scraping. The select-time tool never creates a booking on its own. A human still confirms the form. Our Cal.com API guide covers keys, OAuth and limits in depth.

AI in routing forms and Notes summaries

Routing forms you describe instead of build

Routing forms are a Teams feature, and since the August 2026 release you can build one by chatting. Describe who should go where, and the assistant drafts the fields and the routing logic, reading your organization's attributes so it can route by region, team or deal size. It is a draft, not a finished form. Check every branch against a few real leads before you publish it, because a wrong route sends a prospect to the wrong person without anyone noticing.

Notes: summaries of recorded calls

Cal.com Notes, announced in July 2026, turns every transcribed Cal Video call into a readable summary with no setup. The summary arrives in the transcript email when the call ends and is saved to the booking. Two limits apply. Notes is rolling out through a waitlist, and it will only be on paid plans. Transcription itself sits on team plans and supports English, a multilingual auto-detect option and about 45 named languages. Since August 2026 Cal Video also asks guests for consent before recording and transcription. Recordings and transcripts stay stored until you delete them, so set a cleanup habit.

Privacy, training and the accuracy disclaimer

Cal.com's privacy policy describes its AI features as opt-in and narrow. For meeting notes, only the transcript text goes to the AI provider: no titles, no attendee list, no links. For the phone agent, the provider receives the phone number and the guest details needed to place the call. Nothing is used to train models. The terms go further: Cal.com does not use Customer Data to train or fine-tune generally available AI models, and it requires the same of its AI subprocessors ^[4].

The same terms carry a disclaimer worth reading twice. AI features, Cal.ai included, may produce inaccurate output, and you are responsible for reviewing it before you rely on it. In practice, a phone agent that books the wrong slot is your problem, not the vendor's. Review before you trust. For healthcare, Cal.com's Enterprise page pitches automated voice and SMS reminders inside a HIPAA setup. The usual rule still applies: any third-party integration you add must be HIPAA compliant too.

Four setups worth copying

1. The no-show call for high-value appointments

Add a workflow on your most expensive event type with a before event starts trigger. Send an SMS a day ahead, then let Cal.ai call a few hours before to confirm or reschedule. Set missed calls to leave a voicemail. Keep the call short and the prompt specific. Short calls cost less. Watch the completion and booking rates in the dashboard for two weeks, and read a handful of transcripts, before rolling it out to cheaper appointments.

2. The callback for leads who did not book

Use the routing form trigger for submitted without booking. These are people who told you what they need and then left. A Cal.ai call that offers two open times recovers some of them. Start with one form and one team, because every call spends credits whether it converts or not. Put the form answers in the prompt variables so the agent knows why they came. Then compare the booking rate against the credits spent.

3. Your calendar inside your AI assistant

Connect the hosted MCP server to Claude or Cursor with read-only toolsets first. Use it for a week to ask about your schedule, pull booking details and spot gaps in your availability. Add write tools only once you trust the answers. It costs nothing beyond your plan. If you prefer to keep keys on your own machine, run the local package instead and give it a dedicated API key you can revoke.

4. The team in chat, with summaries after the call

Turn on Cal.com Agents in the Slack or Telegram workspace your team already uses, so people check and move meetings without opening the app. If you record calls on Cal Video, join the Notes waitlist. That way each call ends with a summary on the booking instead of a blank page. Ask guests for consent first. The dialog handles it.

The bottom line

Cal.com's AI story is broad but uneven. The MCP server and Agents are practical, cost nothing extra and suit anyone who already works in Claude, Cursor, Slack or Telegram. The routing form assistant is a handy shortcut, and Notes is promising but still on a waitlist. Cal.ai, the phone agent, is the piece that changes outcomes and the one that costs money: 29 credits a minute, US numbers only, 11 countries, and real value mainly on Teams and above. Start with the free pieces, test the phone agent on one expensive event type, and read the accuracy clause before an agent books for you.