# Calendly MCP server > Check availability, look up events and manage Calendly scheduling from your AI assistant using natural-language requests. - Listing: https://mcp.tc/i/calendly - Connect: use the server's own URL `https://mcp.calendly.com` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Productivity & Projects](https://mcp.tc/c/productivity) - Vendor: Calendly - Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe. - Homepage: ## 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. ## What it can do - 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 ## Example 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." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http calendly https://mcp.calendly.com ``` 2. 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: ```url https://mcp.calendly.com ``` 3. 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: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.calendly.com` and click **Add**. 3. 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 [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "calendly": { "url": "https://mcp.calendly.com" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash 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`: ```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`: ```json { "mcpServers": { "calendly": { "serverUrl": "https://mcp.calendly.com" } } } ``` 2. 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 ```bash codex mcp add calendly --url https://mcp.calendly.com codex mcp login calendly ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.calendly] url = "https://mcp.calendly.com" ``` ### Gemini CLI ```bash 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. ```json { "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`. ## Details - Last checked: 2026-10-03 (reachable, asks for credentials) - Listed: 2026-10-03 - Updated: 2026-10-04 --- Source: https://mcp.tc/i/calendly (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report