calendly

This MCP server provides a Calendly integration that exposes tools for user context, events, invitees, organizations, and a Scheduling API for end-to-end meeting bookings. You can retrieve the current user, list and manage events, view invitees for events, and obtain organization memberships. The Scheduling API adds capabilities to discover event types, check real-time availability, and complete bookings with calendar synchronization and notifications. Use the provided MCP client to call each tool and pass the required parameters (for example, event UUIDs, user or organization URIs, and time windows). The server supports authentication via Personal Access Tokens (PAT) or OAuth 2.0, and you can configure defaults via CALENDLY_USER_URI and CALENDLY_ORGANIZATION_URI for streamlined calls. The available tools are grouped into OAuth 2.0 utilities, API tools (get_current_user, list_events, get_event, list_event_invitees, cancel_event, list_organization_memberships), and Scheduling API tools (list_event_types, get_event_type_availability, and related scheduling operations).

Prerequisites:\n- Node.js and npm installed on your machine.\n- Access to the Calendly API via PAT or OAuth credentials.\n\nOption 1: NPX (Recommended)\n1) Ensure Node.js is installed.\n2) Run the MCP server directly without installation:\nbash\nnpx calendly-mcp-server\n\n\nOption 2: Manual Installation\n1) Clone the repository:\nbash\ngit clone https://github.com/meAmitPatil/calendly-mcp-server.git\ncd calendly-mcp-server\n\n2) Install dependencies:\nbash\nnpm install\n\n3) Build the project (if required by the repo):\nbash\nnpm run build\n

Environment variables: If using PAT, set CALENDLY_API_KEY and optionally CALENDLY_USER_URI and CALENDLY_ORGANIZATION_URI for default contexts. If using OAuth, set CALENDLY_CLIENT_ID, CALENDLY_CLIENT_SECRET, CALENDLY_ACCESS_TOKEN, CALENDLY_REFRESH_TOKEN, and optionally the user/organization URIs. The MCP config example uses NPX to run calendly-mcp-server; you can switch to a local node invocation by pointing to the built server file (e.g., path/to/calendly-mcp-server/dist/index.js). Ensure you handle token security (avoid committing tokens in config files) and consider setting CALENDLY_USER_URI and CALENDLY_ORGANIZATION_URI to optimize calls. If you encounter rate limits or token expiry, use the refresh_token workflow provided by OAuth or rotate PATs as needed.