Calendly — can an agent use it?
Calendly is one of the most agent-ready scheduling tools scored: an official hosted MCP server with 40+ tools, OAuth 2.1 with zero-config dynamic client registration, and developer docs that explicitly serve AI agents. The only real gaps are the absence of agent payment protocols and unpublished API rate limits.
FIND & RETRIEVE · 8.2
ACT & TRANSACT · 6.7
TRUST & DURABILITY · 7.5
FIND & RETRIEVE8.2/10Can an agent get correct information?
Machine-readable surface8/10
Server-rendered HTML with 1,535 words visible without JS. Well-formed llms.txt, JSON-LD (Organization, Product, Offer, FAQPage, WebSite), sitemap with fresh lastmod referenced in robots.txt, and pricing page readable without JS. Missing markdown content negotiation and .well-known/mcp.json card. source
Information retrieval quality8/10
Pricing published in full: Free, Standard $10/seat/mo, Teams $16/seat/mo, Enterprise from $15k/yr. Detailed feature comparison table across tiers. Status page shows 100% uptime. llms.txt provides a structured product index with links to every core feature page. No public API rate-limit numbers. source
Documentation for machines8.5/10
Developer docs at developer.calendly.com include API reference, changelog, getting started guides, OAuth docs, MCP server docs with supported tools list, webhook payloads, and v1-to-v2 migration guide. The docs site header explicitly states: 'For AI agents: a documentation index is available at the root level at /llms.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.' source
ACT & TRANSACT6.7/10Can an agent do the job?
Action coverage8/10
REST API v2 and MCP server expose 40+ tools covering core scheduling: create/update/list event types, book meetings (create_invitee), cancel events, list availability and busy times, create scheduling links (persistent and single-use), manage routing forms, mark no-shows. Booking via create_invitee requires a paid plan. No explicit sandbox or test mode documented. source
Agent protocol support9/10
Official hosted MCP server at mcp.calendly.com with 40+ tools covering the service's core action (scheduling). OAuth 2.1 with Dynamic Client Registration means no pre-registration needed. Dedicated 'Schedule Events with AI Agents' documentation page. Skills discovery endpoints included. This is comprehensive, official, maintained agent protocol support. source
Access & auth friction8/10
Two self-serve paths: Personal Access Tokens for single-account use (instant, no approval) and OAuth 2.1 for multi-account apps. MCP uses OAuth 2.1 with PKCE and Dynamic Client Registration — an agent gets a client_id automatically without pre-registering an OAuth app. Scoped access. Refresh token rotation documented. source
Agent payment capability2/10
No agent payment protocols (ACP, AP2, MPP, x402). Calendly's Payments feature (Stripe/PayPal) is for collecting from meeting invitees, configured by a human in the UI. An agent cannot programmatically purchase a Calendly subscription or set up payment collection. Money only moves when a human configures the payment integration. source
Cost & rate fairness6.5/10
Free tier available. Paid tiers are accessible: Standard $10/seat/mo, Teams $16/seat/mo. API access is part of the product, not separately priced — no agent-vs-human price discrimination. MCP available on Standard+. However, no API rate limits are published in developer docs or terms, making it impossible for an agent to plan capacity. source
TRUST & DURABILITY7.5/10Will it still work next quarter?
Permission & ToS stance7/10
Calendly actively welcomes agent use through sanctioned channels: official MCP server, 'Schedule Events with AI Agents' docs, AI-agent-friendly docs headers. robots.txt restricts marketing-site crawling (Disallow: /*?*, /app/) but allows /llms.txt and /pricing; GPTBot and ClaudeBot both receive HTTP 200. CCBot specifically blocked. Developer Policy prohibits replicating the Calendly UX but does not prohibit API automation. The stance is 'use our official channels, not the site.' source
Reliability & continuity8/10
Public status page at calendlystatus.com showing 100% uptime for calendly.com across Jun-Sep 2026. Separate component tracking for Calendar Integrations, Third Party Integrations, Chrome extension, API and Webhooks. API v2 is the current stable version with a documented v1-to-v2 migration path. Developer changelog exists. source
Sources
Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.
- calendly.com — home — product overview, JSON-LD structured data (accessed 2026-09-09)
- calendly.com/pricing — pricing — Free / $10 / $16 / $15k tiers, feature comparison (accessed 2026-09-09)
- calendly.com/legal/customer-terms-conditions — terms — customer terms effective 05/08/2026 (accessed 2026-09-09)
- calendly.com/robots.txt — robots — allows /llms.txt and /pricing, broad Disallow /*?*, blocks CCBot (accessed 2026-09-09)
- calendly.com/llms.txt — llms — structured product index with core features, AI features, integrations (accessed 2026-09-09)
- developer.calendly.com/docs/getting-started/overview — docs — developer portal with API reference, changelog, MCP, webhooks (accessed 2026-09-09)
- developer.calendly.com/docs/mcp/calendly-mcp-server — mcp — official hosted MCP server at mcp.calendly.com, OAuth 2.1 + DCR (accessed 2026-09-09)
- developer.calendly.com/docs/mcp/supported-tools — mcp-tools — 40+ tools: event types, meetings, availability, routing, scheduling links (accessed 2026-09-09)
- developer.calendly.com/docs/authentication/overview — auth — Personal Access Tokens + OAuth 2.1, DCR for MCP, PKCE, refresh rotation (accessed 2026-09-09)
- calendly.com/legal/developer-policy — dev-policy — prohibits replicating UX, no explicit automation ban (accessed 2026-09-09)
- calendlystatus.com — status — 100% uptime Jun-Sep 2026, component-level tracking (accessed 2026-09-09)