Calendly

What it is

Online booking links. Consultants, coaches, tutors and sales teams send a link and customers pick a time.

How an agent connects

1. Calendly's official MCP server (mcp.calendly.com), fully hosted by Calendly. It signs in with OAuth 2.1 and registers clients automatically (dynamic client registration). A client that asks you to paste a client id and secret will not work with it. It reads event types and availability, creates scheduling links, books events, cancels events and changes availability rules.
2. Calendly API v2 for code an intern builds. It reads and writes scheduling and contact data. Webhooks tell the code when a booking is made or cancelled; verify each one with the Calendly-Webhook-Signature header and reject old timestamps.
3. Zapier triggers on cancellations and new bookings, for an owner's simple automations.

What agents may do

agent_access: read. An agent reads bookings and availability, and may draft a one-time scheduling link for a person to send. It does not book, cancel or reschedule meetings, or change availability.

Through the gateway

The gateway has no Calendly actions yet. Reads use the official server or a read-only API connection. Sending a booking link to a customer goes through gmail.draft or manual.draft and a person's send. Cancelling a customer's booking is never automated.

Watch out for

• The official server's write tools book and cancel real meetings, and Calendly then emails the invitee. Leave them off.
• Invitee answers can hold health, money or legal details, depending on the questions the owner set.
• Webhook signing protects against fake events; Calendly's example uses a three-minute tolerance for replays.
• Calendly's own pages we read do not state API rate limits or which plans include webhooks. Check the owner's plan in their account.