Calendly
Drive Calendly scheduling from any AI agent: list booked events, fetch invitees, query event types, check availability windows, generate single-use scheduling links and cancel meetings. 12 tools, Bearer-token auth.
7 天免费 · 无需信用卡 · EU 托管
问 Calendly 任何事
通过 AnythingMCP 对 Calendly 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 CalendlyClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Calendly。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
Calendly 指南
面向主流 AI 客户端的逐步设置。
配置 Calendly
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
This connector uses the Calendly API v2.
Setup:
- Sign in to https://calendly.com → Integrations & Apps → API & webhooks → Personal Access Tokens → Create new token.
- Give it a name (e.g. 'AnythingMCP'). The token is shown ONCE, copy it immediately. Personal Access Tokens never expire and inherit your user permissions.
- Set
CALENDLY_PERSONAL_ACCESS_TOKENto the token.
Authentication: Bearer token. Calendly also supports OAuth2 for multi-user apps but Personal Access Tokens are the right fit for single-account agent use.
The URI model: every Calendly resource is identified by a full HTTPS URI, NOT a bare ID. For instance a user is https://api.calendly.com/users/AAAAAAAAAAAAAAAA, not just AAAAAAAAAAAAAAAA. List endpoints expect these URIs as query parameters (e.g. ?user=https%3A%2F%2Fapi.calendly.com%2Fusers%2F...). Always grab the URI from a prior tool's response — the easiest starting point is calendly_get_current_user, whose resource.uri is your user URI. Same model for organizations, event types, and scheduled events.
Pagination: cursor-based. Each list response has pagination.next_page_token. Pass it as page_token on the next call.
Cancelling a meeting: counter-intuitively uses POST, not DELETE (POST /scheduled_events/{uuid}/cancellation). Body accepts a reason text that's shown to the invitee. The adapter exposes this as calendly_cancel_scheduled_event.
Availability windows: calendly_list_event_type_available_times returns the open slots between start_time and end_time for an event type. The span MUST be ≤ 7 days; longer ranges return 400. For multi-week scans, call it once per week.
Single-use scheduling links: calendly_create_single_use_scheduling_link produces a URL that can be booked ONCE (max_event_count=1) for a specific event type. Useful when an agent wants to invite one specific person without exposing your generic Calendly profile.
Read-mostly: Calendly's API is heavier on reads than writes. There's no 'create new event type' or 'create new booking on behalf of someone' endpoint — bookings come from invitees clicking a scheduling link.
Rate limits: 100k requests / day per account, with a burst window. On 429, back off.
Webhooks out of scope (/webhook_subscriptions is supported via API but receiving the payloads needs a hosted endpoint).
Plan gating: certain endpoints (organizations, memberships, routing forms) require Teams or Enterprise plans. Personal accounts get 403 — error message identifies the plan required.