Skip to main content
Book a demo

Connect Calendly to Cursor

Give Cursor governed access to Calendly’s 36 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cursor setup guide

Set up

Add Calendly to Cursor in four steps

Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.

  1. 1

    Add Calendly to Runlayer

    Calendly isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Calendly’s 36 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to Calendly

    Sign in the way Calendly requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Calendly from Cursor

    Calendly’s approved tools appear in Cursor. Every call is checked against policy and recorded.

Tools

36 Calendly tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • Availability get user availability schedule

    Use: Fetch details for one named availability schedule.

  • Availability list user availability schedules

    Use: List all named availability schedules for the connected user.

  • Availability list user busy times

    Use: List a user's busy time blocks within a date range.

  • Event types create event type

    Use: Create a new event type on the connected account.

  • Event types get event type

    Use: Fetch full details for one event type by URI.

  • Event types list event type availability schedule

    Use: Read the current availability schedule (rules) for an event type.

  • Event types list event type available times

    Use: List bookable time slots for an event type within a date range.

  • Event types list event types

    Use: List all event types for the connected user or org.

See all 36 Calendly tools

Control

What Runlayer can see and stop in Cursor

Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.

  • Gateway policy (available)

    Every Calendly call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination