Skip to main content
Book a demo

Connect Calendly to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

Add Calendly to GitHub Copilot CLI in four steps

Admins approve the server once. Everyone in GitHub Copilot CLI 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 GitHub Copilot CLI to Runlayer

    Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Calendly’s 36 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI 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 GitHub Copilot CLI

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

Tools

36 Calendly tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI 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 GitHub Copilot CLI

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot CLI 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 or permission request before GitHub Copilot CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.

In GitHub Copilot CLI

  • When a tool fails, Runlayer records the error but cannot replace it.

Frequently asked questions

Connect more

Find another combination