Calendlyvf.sr

listing.by · home.legend.verified

Check availability, look up events and manage Calendly scheduling from your AI assistant using natural-language requests.

state.auth.long (state.auth.title)Streamable HTTP

listing.connect

listing.explain.oauth

https://mcp.calendly.com

listing.note.oauth

listing.share.h

listing.share.p

mcp.tc/i/calendly

listing.about

Connects AI applications to a Calendly account and turns natural-language requests, such as booking a 30-minute meeting next Tuesday, into Calendly API calls. It works with the same scopes and permissions as Calendly's public API, covering scheduling read and write access.

The server is hosted by Calendly at https://mcp.calendly.com over streamable HTTP. Self-hosting is not supported. Users sign in with OAuth 2.1 (authorization code with PKCE) in the browser. The client must support Dynamic Client Registration; personal access tokens and manually provisioned client credentials do not work.

listing.can

  • Check availability for scheduling meetings
  • Look up scheduled events
  • Manage Calendly booking links
  • Turn natural-language requests into Calendly API calls
  • Read and write scheduling data through OAuth scopes

listing.tools

listing.notools.oauth

listing.prompts

  • What meetings do I have scheduled on Calendly this week?

  • Check my availability for next Tuesday afternoon.

  • Book a 30-minute meeting with Sam next Tuesday.

  • Show my Calendly booking links.

listing.setup.h

listing.setup.oauth

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http calendly https://mcp.calendly.com
  1. Start Claude Code, type /mcp, pick calendly and choose Authenticate. A browser window opens for the Calendly sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it Calendly and paste this URL:
https://mcp.calendly.com
  1. Click Add, then Connect, and sign in when Calendly asks.

Claude Desktop's JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://mcp.calendly.com and click Add.
  2. Click Connect and sign in when Calendly asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://mcp.calendly.com as the server URL and choose OAuth. ChatGPT sends you to Calendly to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

Cursor shows Needs login next to the server. Click it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"calendly","type":"http","url":"https://mcp.calendly.com"}'

Or commit it to the repo in .vscode/mcp.json:

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

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "calendly": {
      "serverUrl": "https://mcp.calendly.com"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

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

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.calendly]
url = "https://mcp.calendly.com"

Gemini CLI

gemini mcp add --transport http calendly https://mcp.calendly.com

Then, inside Gemini CLI, run /mcp auth calendly to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI's settings file.

{
  "mcpServers": {
    "calendly": {
      "type": "http",
      "url": "https://mcp.calendly.com"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.calendly.com.

listing.faq

Can I paste mcp.tc/i/calendly into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.calendly.com, so your client talks to Calendly directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Calendly need an API key or a sign-in?

Yes, you need a Calendly account. The first time your client connects, it opens Calendly's sign-in page. The token goes straight to the server's own URL, never through mcp.tc.

Is Calendly a remote or a local server?

Remote. Calendly hosts it at https://mcp.calendly.com, and it speaks Streamable HTTP. There's nothing to install.

What can Calendly do?

You can check availability for scheduling meetings, look up scheduled events and manage Calendly booking links.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc's robot read Calendly's own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![Calendly on mcp.tc](https://mcp.tc/i/calendly/badge.svg)](https://mcp.tc/i/calendly)
HTML
<a href="https://mcp.tc/i/calendly"><img src="https://mcp.tc/i/calendly/badge.svg" alt="Calendly on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/calendly.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/calendly" title="Calendly on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json

https://mcp.tc/i/calendly.json

listing.em.fields

listing.disclaimer_checked