Calendly MCP server for Claude, Codex and Cursor

What your AI apps can do with Calendly

Review scheduled events
Create scheduling links

Calendly MCP tools

36 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`event_types-create_event_type`	Create a new event type
`event_types-update_event_type`	Update an event type
`event_types-list_event_types`	List event types for a user or organization
`event_types-get_event_type`	Get a single event type
`event_types-list_event_type_available_times`	List available time slots for an event type
`event_types-list_event_type_availability_schedule`	List availability schedules for an event type
`event_types-update_event_type_availability_schedule`	Update an event type's availability schedule
`locations-list_user_meeting_locations`	List a user's meeting locations
`meetings-list_events`	List scheduled events
`meetings-get_event`	Get a single scheduled event
`meetings-cancel_event`	Cancel a scheduled event
`meetings-create_invitee`	Book a meeting by creating an invitee (paid plan required)
`meetings-list_event_invitees`	List an event's invitees
`meetings-get_event_invitee`	Get a single event invitee
`scheduling_links-create_single_use_scheduling_link`	Create a single-use scheduling link for an event type
`shares-create_share`	Create a customized one-time link from an event type
`availability-list_user_availability_schedules`	List a user's availability schedules
`availability-get_user_availability_schedule`	Get a single availability schedule
`availability-list_user_busy_times`	List a user's busy times within a range
`meetings-create_invitee_no_show`	Mark an invitee as a no-show
`meetings-get_invitee_no_show`	Get invitee no-show details
`meetings-delete_invitee_no_show`	Remove an invitee no-show mark
`routing_forms-list_routing_forms`	List routing forms (Teams plan or higher)
`routing_forms-get_routing_form`	Get a single routing form (Teams plan or higher)
`routing_forms-list_routing_form_submissions`	List routing form submissions (Teams plan or higher)
`routing_forms-get_routing_form_submission`	Get a single routing form submission (Teams plan or higher)
`users-get_current_user`	Get the signed-in user
`users-get_user`	Get a user by UUID
`organizations-get_organization`	Get organization details
`organizations-list_organization_memberships`	List organization memberships
`organizations-get_organization_membership`	Get a single organization membership
`organizations-list_organization_invitations`	List pending organization invitations
`organizations-create_organization_invitation`	Invite a user to the organization
`organizations-revoke_organization_invitation`	Revoke an organization invitation
`list_calendly_skills`	List available Calendly skills
`load_calendly_skill`	Load a Calendly skill

Suggested access for each AI app

The documentation this list comes from doesn't mark Calendly's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Calendly connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Calendly to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Calendly tool, give Cursor only the read tools, or keep Calendly away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Calendly MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://toolstile.com/mcp'

Then connect Calendly in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Calendly endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http calendly 'https://mcp.calendly.com'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "calendly": {
      "url": "https://mcp.calendly.com"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Calendly MCP documentation for what your client needs.

Before you connect

A Calendly account. Sign-in uses your Calendly permissions.

Server details

Detail	Value
Publisher	Calendly
Endpoint	`https://mcp.calendly.com`
Authentication	Browser sign-in
Categories	Productivity
Tool list	36 tools, observed 29 October 2026 (docs)

Calendly MCP documentation