Independent review. Unpaid; no partnership with Calendly. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Booking pages and scheduling automations, with a free plan. Calendly hosts an official MCP server that signs in with OAuth 2.1, so AI clients can work with scheduling data without API keys in config files.
The Ion perspective
The five-point review
Judgment, not a score. Documentation checked 2026-10-18.
Value
Booking pages and scheduling automations, with a free plan. Calendly hosts an official MCP server that signs in with OAuth 2.1, so AI clients can work with scheduling data without API keys in config files.
Differentiation
Documented fit: Sales and service calls booked from a link; Asking an AI client about upcoming meetings and event types. Uniqueness is not established.
Replaceability and switching
Compare Cal.com, Reclaim. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Clients that need pre-registered OAuth apps (Calendly MCP needs dynamic client registration); Teams needing complex resource scheduling. Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.
Calendly fully hosts the server at mcp.calendly.com; self-hosting isn't supported. It uses OAuth 2.1 with PKCE and dynamic client registration. Clients that only accept console-issued credentials or personal access tokens won't work with it today. source ↗
Plans
Free includes one event type and one calendar connection. Standard is $10 and Teams $16 per seat a month billed yearly. Seats are only needed for hosts, not invitees. Checked 2026-10-18. source ↗
How to use it with AI
How Calendly connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
Not documentedVerify which side exports and which imports, supported formats and permissions. Calendly's recorded upload/import status is no; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route.Claude (incl. Claude Code) file docs ↗
Not documentedOpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Calendly publishes an API, but this pairing still needs network, authentication and execution-scope checks.Calendly API ↗OpenAI Codex docs ↗
InferredOnly in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Calendly is a web app; the pairing itself is not documented.OpenAI Codex browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Calendly's recorded upload/import status is no; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route.OpenAI Codex file docs ↗
InferredThe /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Calendly is a web app; the pairing itself is not documented.Google Antigravity browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Calendly's recorded upload/import status is no; Google Antigravity's file status is yes. These flags do not establish a file-transfer route.Google Antigravity file docs ↗
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
Scheduling with booking pages, routing forms and an API. Its hosted or local MCP server lets authorized AI assistants list, create, reschedule or cancel bookings. Cal.diy is a separate community edition with different capabilities.
Schedules focus time, tasks and habits around meetings. Reclaim 2.0 has an official MCP server for supported AI clients; proposed scheduling changes go to Preview Mode for review before application.