event_types-create_event_typeLABSCO SUMMARY
Dynamic client registration is elegant and it is also the compatibility check to make first.
Nothing to provision means nothing to leak, and the read and write scopes let a diary-reading assistant be genuinely read-only. But the requirement is real: if your client asks you to paste a client id, it will not work here, and no amount of configuration changes that. Check the client before planning the integration. Single-use booking links are the tool worth knowing about — they let an agent hand out one appointment without exposing a permanent calendar link.
What it is
Calendly's own hosted endpoint, mapping their public API v2. Officially hosted only — self-hosting is not supported.
What you get
- List event types and check available times
- Adjust scheduling availability
- Fetch scheduling links, and generate single-use booking links
- Create and cancel scheduled events
Requirements
OAuth 2.1 with PKCE and dynamic client registration — the client registers itself, so there are no credentials to pre-provision. That is also the constraint: a client that needs a manually entered client id and secret cannot connect at all. Scopes split read from write.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Finding a time without opening the calendar
List the event types and read the available slots directly.
02
Sending someone a one-off link
Generate a single-use booking link instead of sharing a permanent one.
03
Giving an assistant read-only diary access
Grant mcp:scheduling:read alone, so it can answer questions but not book.
36 tools
Listed in project docs. Your client may show a different list.
event_types-update_event_typeevent_types-list_event_typesevent_types-get_event_typeevent_types-list_event_type_available_timesevent_types-list_event_type_availability_scheduleevent_types-update_event_type_availability_schedulelocations-list_user_meeting_locationsmeetings-list_eventsmeetings-get_eventmeetings-cancel_eventmeetings-create_inviteemeetings-list_event_inviteesmeetings-get_event_inviteescheduling_links-create_single_use_scheduling_linkshares-create_shareavailability-list_user_availability_schedulesavailability-get_user_availability_scheduleavailability-list_user_busy_timesmeetings-create_invitee_no_showmeetings-get_invitee_no_showmeetings-delete_invitee_no_showrouting_forms-list_routing_formsrouting_forms-get_routing_formrouting_forms-list_routing_form_submissionsrouting_forms-get_routing_form_submissionusers-get_current_userusers-get_userorganizations-get_organizationorganizations-list_organization_membershipsorganizations-get_organization_membershiporganizations-list_organization_invitationsorganizations-create_organization_invitationorganizations-revoke_organization_invitationlist_calendly_skillsload_calendly_skillBEFORE YOU INSTALL
What to know first
Tools you get
36 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.1 authorization code with PKCE and Dynamic Client Registration (RFC 7591) — the client registers itself at runtime, with no pre-issued credentials; scopes mcp:scheduling:read and mcp:scheduling:write
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.calendly.comRequirements
- OAuth 2.1 authorization code with PKCE and Dynamic Client Registration (RFC 7591) — the client registers itself at runtime, with no pre-issued credentials; scopes mcp:scheduling:read and mcp:scheduling:write
