# Calendly

> Booking-link scheduling — share availability without exposing the raw calendar.

[Canonical HTML page](https://top-mcps.com/mcp/calendly) · [server.json](https://top-mcps.com/mcp/calendly.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "calendly": {
      "command": "npx",
      "args": [
        "-y",
        "calendly-mcp"
      ],
      "env": {
        "CALENDLY_API_TOKEN": "${CALENDLY_API_TOKEN}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export CALENDLY_API_TOKEN=YOUR_API_TOKEN
claude mcp add calendly -- npx -y calendly-mcp
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "calendly": {
      "command": "npx",
      "args": [
        "-y",
        "calendly-mcp"
      ],
      "env": {
        "CALENDLY_API_TOKEN": "${CALENDLY_API_TOKEN}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "calendly": {
      "command": "npx",
      "args": [
        "-y",
        "calendly-mcp"
      ],
      "env": {
        "CALENDLY_API_TOKEN": "${CALENDLY_API_TOKEN}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "calendly": {
      "command": "npx",
      "args": [
        "-y",
        "calendly-mcp"
      ],
      "env": {
        "CALENDLY_API_TOKEN": "${CALENDLY_API_TOKEN}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "calendly": {
      "command": "npx",
      "args": [
        "-y",
        "calendly-mcp"
      ],
      "env": {
        "CALENDLY_API_TOKEN": "${CALENDLY_API_TOKEN}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "calendly-mcp"
          ],
          "env": {
            "CALENDLY_API_TOKEN": "${CALENDLY_API_TOKEN}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.calendly]
command = "npx"
args = [
  "-y",
  "calendly-mcp",
]
env = { CALENDLY_API_TOKEN = "${CALENDLY_API_TOKEN}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "calendly": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "calendly-mcp"
        ]
      },
      "env": {
        "CALENDLY_API_TOKEN": "${CALENDLY_API_TOKEN}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Apps directory`

Calendly doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

```none

```

## At a glance

- **Maintainer:** Community
- **Transport:** stdio
- **Auth model:** OAuth 2.1
- **Required secrets:** CALENDLY_API_TOKEN
- **Supported clients:** Claude, Cursor, Any MCP-compatible client
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-05-26
- **Score:** 53/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/calendly/mcp-server

## Security & scope

- **Access scope:** read-write
- **Sandbox:** OAuth tokens scope to the user's account. Organization-level operations require an org-scoped token.
- **Gotchas:**
  - PATs are account-wide; rotate frequently.
  - Webhook subscriptions persist beyond the MCP session — clean up if no longer used.

## Quick answer

**What it does.** Provides MCP tools for listing event types, retrieving scheduled events, fetching availability windows, and managing Calendly's organization-level entities.

**Best for:**
- External booking workflows
- Recruiter and sales flows
- Read-only upcoming-meetings views
- Cancellation and rescheduling automation

**Not for:**
- Internal team scheduling
- Workflows requiring deep calendar manipulation

## Description

The Calendly MCP exposes Calendly's booking and event-management APIs. The agent can list event types, fetch a sharable link, query upcoming bookings, and cancel or reschedule on the user's behalf — useful for assistant flows that bridge a user's calendar with external parties.

## Why it matters

Calendly remains the most-used external scheduling tool in business contexts. The MCP version turns "send me a Calendly link" from a tab-switch into a one-step assistant operation.

## Key features

- Event-type management
- Availability queries
- Scheduled-event listing
- Webhook subscription
- OAuth 2 auth

## FAQ

### Do I need a paid Calendly plan?

Free plan covers personal use; team and org features (round-robin, workflows) require paid plans. API access works on all tiers.

### Can the agent cancel a meeting?

Yes via the `cancel` tool. The MCP requires that the agent confirm with the user before invoking destructive operations.

### Why is OAuth recommended over API key?

Calendly's OAuth model scopes access per organization and supports revocation. Personal Access Tokens work but are account-wide.

## Changelog

- **2026-05-26** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-03-05** — Initial directory listing.