Calendly MCP server for your AI

One value: a Personal Access Token, pasted into the Personal Access Token field on the connect form. There is no OAuth app to register, no redirect URL and no client secret, and the connection works the moment the token is saved. The token authenticates as you over HTTPS, so the agent reaches what your own Calendly account reaches.

No. PopMCP auto-detects your user and organization from the token and applies the right scope to every request, so listing event types, scheduled events and invitees works with no extra setup, and get_current_user will tell you who the token belongs to. The one thing that catches people out is the ID format: tools like get_user, get_scheduled_event and get_group take the UUID, which is the trailing segment of a Calendly resource URI, not the full URI string.

41 operations across 12 API modules, split 29 read and 12 write, plus 13 triggers PopMCP can watch. The 24 most-used tools load into your AI client by default and the rest stay searchable, so the tool list does not crowd out your other connections. The modules are organizations, scheduled events, webhooks, event types, groups, routing forms, invitee no-shows, availability, identity, data compliance, scheduling links and the activity log.

They can only return what your plan includes. Groups and group relationships are Teams and Enterprise features, and the activity log is an Enterprise feature, so list_groups, list_group_relationships and the activity log tool are only useful on an account that has them. A Personal Access Token cannot grant access your plan does not already include, so if one of those calls comes back empty, check the plan before you suspect the connection.

Both. list_user_availability_schedules returns a user's weekly working hours, while list_user_busy_times returns their busy intervals over a date range, covering internal Calendly events plus connected calendars. For booking questions, pair either with list_event_type_available_times, which returns the open slots on a specific event type within a date range.

The access mode and the approval setting on the connection. A read-only connection can still report on meetings, invitees and no-shows but cannot call cancel_scheduled_event, remove_organization_membership or either GDPR tool; on a full-access connection, approval-required-for-writes holds each of those for your sign-off. Treat the GDPR tools as the ones to gate hardest, since delete_invitee_data permanently removes invitee data for the given email addresses across the organization. No-show marks are the reversible case: delete_invitee_no_show simply un-marks the invitee.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server — Claude Desktop, Claude Web, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Loading 41 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 24-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. You can switch a connection to the full catalog at any time.

A tool is something your AI calls — there are 41 here. A trigger is something PopMCP watches for you: 13 Calendly events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Calendly.