Skip to main content
Glama

@nimblebraininc/calendly

MCP server for the Calendly API. Browse event types, view and filter scheduled meetings, inspect invitee details, check availability windows, and cancel events.

Tools

Tool

Description

get_current_user

Get the authenticated user's profile

list_event_types

List the user's event types

list_scheduled_events

List scheduled events with optional filters

get_event

Get details of a specific scheduled event

list_invitees

List invitees for a scheduled event

cancel_event

Cancel a scheduled event with an optional reason

check_availability

Get available time slots for an event type

Related MCP server: Calendly MCP Server

Setup

  1. Get a Personal Access Token from Calendly Integrations

  2. Configure via mpak:

    mpak config set @nimblebraininc/calendly api_key your_token_here

Development

npm install
npm run build
npm run check     # format, lint, typecheck, tests

License

MIT

Available Tools

7 tools
cancel_eventB
Destructive

Cancel a scheduled Calendly event

Inputs: event_uuid (required), reason.

check_availabilityB
Read-only

Get available time slots for an event type

Inputs: event_type_uri (required), start_time (required), end_time (required).

get_current_userA
Read-only

Get the authenticated Calendly user's profile

Inputs: no named parameters.

get_eventB
Read-only

Get details of a specific scheduled event

Inputs: event_uuid (required).

list_event_typesB
Read-only

List the user's Calendly event types

Inputs: count, page_token.

list_inviteesB
Read-only

List invitees for a scheduled event

Inputs: event_uuid (required), count, page_token.

list_scheduled_eventsA
Read-only

List scheduled Calendly events with optional filters

Inputs: count, page_token, status, min_start_time, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific resources and actions in the Calendly domain. For example, 'get_event' retrieves details of a single event, while 'list_scheduled_events' lists multiple events with filters, and 'cancel_event' performs a distinct cancellation action. There is no overlap or ambiguity in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with clear, descriptive actions (e.g., 'cancel_event', 'get_current_user', 'list_event_types'). The naming is uniform across all seven tools, using snake_case consistently without any deviations or mixed conventions.

    Tool Count5/5

    With 7 tools, this server is well-scoped for managing Calendly events and user interactions. The count is appropriate for the domain, covering core operations like checking availability, listing events, and managing event details without being overly sparse or bloated.

    Completeness4/5

    The tool set provides strong coverage for core Calendly workflows, including event listing, retrieval, cancellation, availability checks, and user profile access. A minor gap exists in the lack of a tool for creating or scheduling new events, which agents might need to work around, but the surface is otherwise comprehensive for the inferred domain.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers