topmcps
Browse MCPs
Calendly

Calendly

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

Score 53(?)CommunityMITVerified Top MCPs for Scheduling & Calendar →
InstallView on GitHub

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

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

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

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

    CLI or .mcp.json
    # export CALENDLY_API_TOKEN=YOUR_API_TOKEN
claude mcp add calendly -- npx -y calendly-mcp

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

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

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

    .vscode/mcp.json
    {
  "servers": {
    "calendly": {
      "command": "npx",
      "args": [
        "-y",
        "calendly-mcp"
      ],
      "env": {
        "CALENDLY_API_TOKEN": "${CALENDLY_API_TOKEN}"
      }
    }
  }
}

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

    ~/.codeium/windsurf/mcp_config.json
    {
  "mcpServers": {
    "calendly": {
      "command": "npx",
      "args": [
        "-y",
        "calendly-mcp"
      ],
      "env": {
        "CALENDLY_API_TOKEN": "${CALENDLY_API_TOKEN}"
      }
    }
  }
}

    Open via Cascade → hammer icon → Configure.

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

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "calendly-mcp"
          ],
          "env": {
            "CALENDLY_API_TOKEN": "${CALENDLY_API_TOKEN}"
          }
        }
      }
    ]
  }
}

    Continue uses modelContextProtocolServers with a transport block.

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

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

    ~/.config/zed/settings.json
    {
  "context_servers": {
    "calendly": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "calendly-mcp"
        ]
      },
      "env": {
        "CALENDLY_API_TOKEN": "${CALENDLY_API_TOKEN}"
      }
    }
  }
}

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

    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.

  2. 2

    Set required secrets

    Set CALENDLY_API_TOKEN in your shell environment before launching your MCP client.

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

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 [Cal.com 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 Cal.com
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 (CALENDLY_API_TOKEN) 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.

google-calendarschedulingeventsproductivity
10 minMedium
Outlook Calendar logo — MCP server
Official

Outlook Calendar — official ChatGPT Apps directory listing, verified for 2026.

outlook-calendarchatgpt-appofficialapps-directory
< 1 minLow
Cal.com
Official

Open-source scheduling — booking pages, availability, and event types for AI agents.

calendarschedulingcal-combooking
5 minLow

Compared with Calendly

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

CalendlyvsGoogle CalendarCalendlyvsCal.comCalendlyvsOutlook CalendarCalendlyvsTodoist

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