# Calendly MCP MCP Server > **Calendly MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Calendly MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/calendly-mcp > MewCP docs: https://docs.mewcp.com > All servers: https://mewcp.com/servers (JSON: https://mewcp.com/api/servers) > About MewCP: https://mewcp.com/llms.txt --- ## About Connect AI assistants to Calendly for seamless meeting scheduling and calendar management. Check real-time availability, book and reschedule meetings, manage event types, and generate personalized scheduling links—all through natural language. --- ## Details - Server ID: `calendly-mcp` - Version: 3.3.1 - Tools: 36 - Authentication: OAuth, managed by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Calendly MCP has to be in the toolset first. In order: 1. Add Calendly MCP to your toolset at https://mewcp.com/mcp/calendly-mcp 2. Connect your Calendly MCP account (OAuth); MewCP stores the credential and attaches it to each call 3. Add the gateway URL to your client (see Connect below). It signs in with OAuth the first time it connects, so there is no key to copy. Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (36) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `availability-list_user_availability_schedules` _(read)_ — Use: List all named availability schedules for the connected user. When: User asks about availability schedules or you need to identify one by name. Needs:… - `availability-get_user_availability_schedule` _(read)_ — Use: Fetch details for one named availability schedule. When: User asks about specific schedule rules or needs rules for a named schedule. Needs: Schedule URI… - `availability-list_user_busy_times` _(read)_ — Use: List a user's busy time blocks within a date range. When: User asks a general yes/no "what's my schedule", "am I free/busy", or "do I have any meetings"… - `event_types-create_event_type` _(write)_ — Use: Create a new event type on the connected account. When: User explicitly asks to create a new event type. Needs: Host user URI from… - `event_types-update_event_type` _(destructive)_ — Use: Update fields on an existing event type. When: User asks to change name, duration, description, or other settings. Needs: Event type URI from… - `event_types-list_event_types` _(read)_ — Use: List all event types for the connected user or org. When: Start of any event-type task, or when selecting an event type by name. Needs: User URI from… - `event_types-get_event_type` _(read)_ — Use: Fetch full details for one event type by URI. When: Before updating an event type or confirming its current configuration. Needs: Event type URI. Do: Use… - `event_types-list_event_type_available_times` _(read)_ — Use: List bookable time slots for an event type within a date range. When: User wants slots, or to confirm availability before booking. Needs: Event type URI… - `event_types-list_event_type_availability_schedule` _(read)_ — Use: Read the current availability schedule (rules) for an event type. When: Before calling `event_types-update_event_type_availability_schedule`. Needs: Event… - `event_types-update_event_type_availability_schedule` _(destructive)_ — Use: Overwrite the availability schedule for an event type. When: User requests schedule changes (hours, days, one-off date overrides) for an event type.… - `locations-list_user_meeting_locations` _(read)_ — Use: List allowed meeting location kinds for a user. When: Before creating bookings that need a `location` payload. Needs: User URI from… - `meetings-list_events` _(read)_ — Use: List scheduled meetings for user/org. When: Upcoming/past meetings or to find meetings by date. Needs: User/org URI via `users-get_current_user`. Do:… - `meetings-get_event` _(read)_ — Use: Fetch details for a single scheduled meeting. When: User asks about a specific meeting or before canceling/examining invitees. Needs: Meeting URI from… - `meetings-cancel_event` _(destructive)_ — Use: Cancel a scheduled meeting on behalf of the connected host When: User confirms they want to cancel a specific meeting. Needs: Meeting URI from… - `meetings-create_invitee` _(destructive)_ — Use: Book a meeting slot for an invitee on a Calendly event type. When: User provides invitee name, email, and a confirmed available time slot. Needs: Event… - `meetings-list_event_invitees` _(read)_ — Use: List all invitees for a scheduled meeting. When: User asks who is attending a meeting or you need invitee URIs. Needs: Meeting URI from… - `meetings-get_event_invitee` _(read)_ — Use: Fetch details for a single meeting invitee. When: User asks about a specific attendee's booking details. Needs: Meeting URI from `meetings-list_events`… - `meetings-create_invitee_no_show` _(write)_ — Use: Mark an invitee as a no-show for a past meeting. When: User reports an invitee did not attend. Needs: Invitee URI from `meetings-list_event_invitees`. Do:… - `meetings-get_invitee_no_show` _(read)_ — Use: Fetch the no-show record for a meeting invitee. When: User asks whether a no-show was recorded for an invitee. Needs: No-show URI from… - `meetings-delete_invitee_no_show` _(destructive)_ — Use: Remove a no-show mark from an invitee. When: User asks to undo a no-show marking. Needs: No-show URI from `meetings-create_invitee_no_show`. Do: Pass… - `organizations-get_organization` _(read)_ — Use: Fetch details for the connected user's organization. When: User asks about the org or you need the org URI for org-scoped list tools. Needs: Org URI from… - `organizations-list_organization_memberships` _(read)_ — Use: List all members of an organization. When: User asks who is in the org or you need to find a member's user URI. Needs: Org URI from… - `organizations-get_organization_membership` _(read)_ — Use: Fetch details for a single org membership. When: You need role or status for a specific member. Needs: Membership URI from… - `organizations-list_organization_invitations` _(read)_ — Use: List pending invitations for the organization. When: User asks to see pending invites or check if someone was already invited. Needs: Org URI from… - `organizations-create_organization_invitation` _(write)_ — Use: Invite a user to the organization by email. When: User asks to add a new member. Needs: Org URI and invitee email address. Do: Check… - `organizations-revoke_organization_invitation` _(destructive)_ — Use: Revoke a pending organization invitation. When: User asks to cancel a pending invite. Needs: Organization URI from `users-get_current_user` and Invitation… - `routing_forms-list_routing_forms` _(read)_ — Use: List routing forms for the org. When: User asks about routing forms or you need to find a form by name. Needs: Org URI from `users-get_current_user`. Do:… - `routing_forms-get_routing_form` _(read)_ — Use: Fetch details for a single routing form. When: User asks about a specific form or its questions. Needs: Routing form URI from… - `routing_forms-list_routing_form_submissions` _(read)_ — Use: List submissions for a routing form. When: User asks to see form responses or analyze routing data. Needs: Routing form URI from… - `routing_forms-get_routing_form_submission` _(read)_ — Use: Fetch details for a single routing form submission. When: User asks about a specific submission or response. Needs: Submission URI from… - `scheduling_links-create_single_use_scheduling_link` _(write)_ — Use: Create a single-use scheduling link using the event type's settings unchanged. When: User wants a one-time link with no overrides. For per-link… - `shares-create_share` _(read)_ — Use: Create a single-use share link for a one-on-one event type with per-link overrides When: User wants a single-use link with any customization (duration,… - `users-get_current_user` _(read)_ — Use: Resolve the connected host account and canonical user URI. When: Start any scheduling, booking, event-type, or availability workflow. Needs: No inputs.… - `users-get_user` _(read)_ — Use: Fetch profile for a specific user by URI. When: User asks about another person's account or you hold a user URI from org/membership data. Needs: User URI.… - `list_calendly_skills` _(read)_ — List or search available Calendly skill guides. Each skill gives domain-specific context, recommended tool usage, and best practices for working with Calendly… - `load_calendly_skill` _(read)_ — Load a Calendly skill guide that provides domain-specific context, recommended queries, and best practices for working with Calendly tools. Required after… --- ## Connect - URL: https://gateway.mewcp.com/personal/mcp - Transport: Streamable HTTP (remote). Nothing to install. - Sign-in: OAuth. On first connect the client opens a browser window to sign in to MewCP and approve access. No API key. - Headless clients (SDKs, servers without a browser) send an API key instead: `Authorization: Bearer `, key from https://mewcp.com/dashboard/api-keys Agents setting themselves up: follow https://mewcp.com/SKILL.md Step-by-step guide per client: - Claude Desktop: https://mewcp.com/mcp/calendly-mcp/connect/claude - ChatGPT: https://mewcp.com/mcp/calendly-mcp/connect/chatgpt - VS Code: https://mewcp.com/mcp/calendly-mcp/connect/vscode - Cursor: https://mewcp.com/mcp/calendly-mcp/connect/cursor - Codex: https://mewcp.com/mcp/calendly-mcp/connect/codex - Claude Code: https://mewcp.com/mcp/calendly-mcp/connect/claude-code - OpenCode: https://mewcp.com/mcp/calendly-mcp/connect/opencode - OpenClaw: https://mewcp.com/mcp/calendly-mcp/connect/openclaw - Antigravity: https://mewcp.com/mcp/calendly-mcp/connect/antigravity - Hermes: https://mewcp.com/mcp/calendly-mcp/connect/hermes - DeepSeek Harness: https://mewcp.com/mcp/calendly-mcp/connect/dsh - Python: https://mewcp.com/mcp/calendly-mcp/connect/python - TypeScript: https://mewcp.com/mcp/calendly-mcp/connect/typescript