Calendly

Calendly

Official hosted MCP for booking-link scheduling — share availability without exposing the raw calendar.

Score 46(?)CalendlyProprietaryVerified Top MCPs for Scheduling & Calendar →

Quick answer

What it does

Calendly's hosted MCP exposes tools for listing event types, retrieving scheduled events, checking availability windows, generating booking links, and cancelling events — full coverage of the Calendly API v2 scheduling surface.

Best for

  • External booking workflows
  • Recruiter and sales flows
  • Read-only upcoming-meetings views
  • Cancellation and rescheduling automation

Not for

  • Internal team scheduling
  • Self-hosted or air-gapped deployments (hosted-only)

Source: top-mcps.com/mcp/calendly — verified Sep 2026

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
      "mcpServers": {
        "calendly": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://mcp.calendly.com"
          ]
        }
      }
    }

    Claude Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint and opens the sign-in in your browser. On Pro, Max, Team and Enterprise you can skip the file: Settings → Connectors → Add custom connector → https://mcp.calendly.com. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI or .mcp.json
    claude mcp add --transport http calendly https://mcp.calendly.com

    Then run /mcp inside Claude Code to finish the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    .cursor/mcp.json
    {
      "mcpServers": {
        "calendly": {
          "url": "https://mcp.calendly.com"
        }
      }
    }

    Global path: ~/.cursor/mcp.json. Cursor shows "Needs login" once it connects — click it to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    .vscode/mcp.json
    {
      "servers": {
        "calendly": {
          "type": "http",
          "url": "https://mcp.calendly.com"
        }
      }
    }

    VS Code uses the "servers" key. Run MCP: List Servers → Start Server and allow the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "calendly": {
          "serverUrl": "https://mcp.calendly.com"
        }
      }
    }

    Windsurf uses "serverUrl" for hosted servers. Open via Cascade → hammer icon → Configure. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    cline_mcp_settings.json
    {
      "mcpServers": {
        "calendly": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://mcp.calendly.com"
          ]
        }
      }
    }

    Bridged through mcp-remote. Open via the Cline sidebar → MCP Servers → Edit. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.continue/config.json
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "streamable-http",
              "url": "https://mcp.calendly.com"
            }
          }
        ]
      }
    }

    Continue takes the hosted URL directly in the transport block. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI
    codex mcp add calendly --url https://mcp.calendly.com

    Codex detects OAuth support and opens the browser to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "calendly": {
          "command": {
            "path": "npx",
            "args": [
              "-y",
              "mcp-remote",
              "https://mcp.calendly.com"
            ]
          }
        }
      }
    }

    Bridged through mcp-remote under "context_servers". Settings live-reload on save. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ChatGPT → Settings → Connectors (remote URL)
    {
      "name": "Calendly",
      "transport": "http",
      "url": "https://mcp.calendly.com"
    }

    Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled.

  2. 2

    Set required secrets

    No credentials required — this MCP runs over stdio without authentication.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope
Read + write
Sandbox
OAuth 2.1 (Authorization Code + PKCE) scopes access to the authenticated Calendly account; the server is hosted by Calendly so no token sits on the user's machine beyond the client's own OAuth cache.
Gotchas
  • Hosted-only: there is no self-host or local deployment path.
  • Requires an MCP client that supports Dynamic Client Registration (DCR); clients that need a pasted client_id will not connect.
  • Personal access tokens / non-OAuth bearer tokens are not accepted.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. scheduling & calendar work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-scheduling-calendar
Compare Calendly against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Calendly MCP vs [Google Calendar MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/calendly
- top-mcps.com listing for Google Calendar
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Calendly MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/calendly (fetch https://top-mcps.com/mcp/calendly.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets () and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.
  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Scheduling & Calendar MCPs

Other tools in the same category worth evaluating.

Google Calendar31

Read, create, and manage events across Google Calendar — via Google's official remote MCP or a self-hosted community server.

google-calendar, scheduling, events, productivity
10 minMedium
Apple Calendar (CalDAV)

Read and create events in Apple Calendar via CalDAV from any MCP client.

calendar, apple, caldav, icloud
10 minMedium
Cal.com
Official

Official Cal.com hosted MCP — AI agents book, reschedule, and query availability across 34 tools via OAuth 2.1, no local install.

cal.com, scheduling, booking, calendar
5 minLow

Compared with Calendly

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Exploring Top MCPs for Scheduling & Calendar? See all Scheduling & Calendar MCPs →