Calendly

Overview

Property	Value
Slug	`calendly`
Category	Calendar
Auth	API key — Personal Access Token (Bearer)
Base URL	`https://api.calendly.com`
Tool count	47
Rate limit	2 req/sec, 100 req/min

Supported tools

All 47 slugs surfaced through MCP:

Area	Slugs
Users	`CALENDLY_GET_ME`, `CALENDLY_GET_USER`
Event types	`CALENDLY_LIST_EVENT_TYPES`, `CALENDLY_GET_EVENT_TYPE`, `CALENDLY_CREATE_EVENT_TYPE`, `CALENDLY_CREATE_ONE_OFF_EVENT_TYPE`, `CALENDLY_UPDATE_EVENT_TYPE`, `CALENDLY_LIST_EVENT_TYPE_HOSTS`
Availability	`CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES`, `CALENDLY_LIST_USER_BUSY_TIMES`, `CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES`, `CALENDLY_GET_USER_AVAILABILITY_SCHEDULE`, `CALENDLY_LIST_EVENT_TYPE_AVAILABILITY_SCHEDULES`, `CALENDLY_UPDATE_EVENT_TYPE_AVAILABILITY_SCHEDULES`
Scheduled events	`CALENDLY_LIST_SCHEDULED_EVENTS`, `CALENDLY_GET_SCHEDULED_EVENT`, `CALENDLY_CANCEL_SCHEDULED_EVENT`
Invitees	`CALENDLY_LIST_EVENT_INVITEES`, `CALENDLY_GET_EVENT_INVITEE`, `CALENDLY_CREATE_INVITEE`
No-shows	`CALENDLY_MARK_INVITEE_NO_SHOW`, `CALENDLY_GET_INVITEE_NO_SHOW`, `CALENDLY_DELETE_INVITEE_NO_SHOW`
Scheduling links & shares	`CALENDLY_CREATE_SCHEDULING_LINK`, `CALENDLY_CREATE_SHARE`
Locations	`CALENDLY_LIST_USER_MEETING_LOCATIONS`
Contacts	`CALENDLY_LIST_CONTACTS`, `CALENDLY_CREATE_CONTACT`, `CALENDLY_GET_CONTACT`, `CALENDLY_UPDATE_CONTACT`, `CALENDLY_DELETE_CONTACT`
Organizations	`CALENDLY_GET_ORGANIZATION`, `CALENDLY_LIST_ORGANIZATION_MEMBERSHIPS`, `CALENDLY_GET_ORGANIZATION_MEMBERSHIP`, `CALENDLY_REMOVE_ORGANIZATION_MEMBERSHIP`, `CALENDLY_INVITE_USER_TO_ORGANIZATION`, `CALENDLY_LIST_ORGANIZATION_INVITATIONS`, `CALENDLY_GET_ORGANIZATION_INVITATION`, `CALENDLY_REVOKE_ORGANIZATION_INVITATION`
Groups	`CALENDLY_LIST_GROUPS`, `CALENDLY_GET_GROUP`, `CALENDLY_LIST_GROUP_RELATIONSHIPS`, `CALENDLY_GET_GROUP_RELATIONSHIP`
Data compliance	`CALENDLY_DELETE_INVITEE_DATA`, `CALENDLY_DELETE_SCHEDULED_EVENT_DATA`
Activity log	`CALENDLY_LIST_ACTIVITY_LOG_ENTRIES`
Outgoing communications	`CALENDLY_LIST_OUTGOING_COMMUNICATIONS`

Connect setup

Unlike OAuth providers, Calendly connects with a Personal Access Token — there is no redirect or consent screen. Each end user supplies their own token, which is stored encrypted and sent as a Bearer token.

Create a Calendly Personal Access Token

In Calendly, go to Integrations & apps → API & webhooks → Personal access tokens and create a token. Copy it — it’s shown only once. (Requires a paid Calendly plan. Do not use a legacy v1 API key.)

Open the connect form

When the agent needs Calendly and it isn’t connected yet, it surfaces a Connect action. The form asks for a single field — your Calendly Personal Access Token.

Submit

On submit, RouteMCP stores the token (encrypted at rest) and marks the connection active immediately — no redirect. Use Disconnect to remove it.

Usage

Through the chat endpoint (recommended)

# Book a meeting (the agent checks availability first, then books)
curl -N -X POST "https://api.routemcp.io/api/v1/mcp/<workspace_id>/chat" \
  -H "x-api-key: sk_live_your_key" \
  -H "x-session-id: user-42" \
  -H "content-type: application/json" \
  -d '{"message": "Book my 30-minute intro call tomorrow at 2pm with alice@example.com."}'

# Read upcoming meetings
curl -N -X POST "https://api.routemcp.io/api/v1/mcp/<workspace_id>/chat" \
  -H "x-api-key: sk_live_your_key" \
  -H "x-session-id: user-42" \
  -H "content-type: application/json" \
  -d '{"message": "What Calendly meetings do I have this week?"}'

Direct MCP JSON-RPC (Claude Desktop / Cursor / custom MCP clients)

{
  "mcpServers": {
    "routemcp": {
      "url": "https://api.routemcp.io/api/v1/mcp/<workspace_id>",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>",
        "x-session-id": "<SESSION_ID>"
      }
    }
  }
}

Once connected, MCP clients can invoke any of the 47 tools by slug via the standard tools/call JSON-RPC method.

Overview

CRM

Accounting

Calendar

Developer

Productivity

Documents & Storage

Communication

Project Management

Database

Overview

Supported tools

Connect setup

Usage

Through the chat endpoint (recommended)

Direct MCP JSON-RPC (Claude Desktop / Cursor / custom MCP clients)

​Overview

​Supported tools

​Connect setup

​Usage

​Through the chat endpoint (recommended)

​Direct MCP JSON-RPC (Claude Desktop / Cursor / custom MCP clients)

Overview

Supported tools

Connect setup

Usage

Through the chat endpoint (recommended)

Direct MCP JSON-RPC (Claude Desktop / Cursor / custom MCP clients)