Skip to main content

Connect Calendly to OpenCode

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

Set up

Add Calendly to OpenCode in four steps

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

    Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Calendly’s 36 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    OpenCode 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 OpenCode

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

Tools

36 Calendly tools in OpenCode

Runlayer policy decides which of these OpenCode 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 OpenCode

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination