6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Book, cancel and reschedule meetings, edit event types and adjust availability.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Calendly MCP server connects a Calendly account to Claude, ChatGPT and any MCP-compatible agent. Thirty-six tools list availability, create and edit event types, generate scheduling links, book meetings and cancel them — so scheduling happens in conversation rather than in the Calendly app. Sign-in is OAuth, and read and write are separate scopes.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
meetings-cancel_event is in both Anthropic's listing and Calendly's own table, mapped to the cancellation endpoint. Cancelling is not a local state change — the person who booked receives a Calendly cancellation email. No server-side confirmation step is documented, so whether you are asked first is entirely your MCP client's tool-approval setting.reschedule_url for the invitee to use, or cancelling and rebooking — which generates two emails, not a quiet move.meetings-list_event_invitees and meetings-get_event_invitee return invitee records, which Calendly's own AI agents guide shows carrying name, email address, timezone, questions_and_answers from your booking form, tracking parameters and cancel/reschedule URLs. Those are third parties' details, and once read they live wherever your assistant's conversation history lives. Calendly's own QA checklist advises that logs redact PII — advice worth extending to the transcript.meetings-create_invitee needs a paid plan, and all four routing_forms-* tools need Teams or above. Connecting is free; those six tools are not. Everything else works on Free.mcp:scheduling:write covers creating event types, editing availability, booking, cancelling, inviting organization members and generating links, in one grant. And because Calendly documents that :write implicitly includes :read, there is no write-without-read option either.client_id and client_secret will not work today. Personal access tokens are also explicitly unsupported for MCP, though they remain valid for Calendly's REST API./mcp. The endpoint is the bare host with a trailing slash. We verified on 2026-08-18 that https://mcp.calendly.com/mcp returns HTTP 404 while the bare host returns a 401 challenge.webhooks:read and webhooks:write, but neither is among the two MCP scopes and no webhook tool appears in either tool list. Real-time notification of bookings and cancellations stays a REST-API job, and Calendly's FAQ notes webhook subscriptions need a paid Standard, Teams or Enterprise plan.readOnlyHint, destructiveHint and idempotentHint, but that is its claim, not our observation.Any plan, including Free, for most of it. Calendly's developer FAQ states that GET and POST requests can be made on behalf of a user on any subscription plan, with a few Enterprise-only endpoints excepted, and that webhook subscriptions require a paid Standard, Teams or Enterprise plan. Calendly's help centre says the same for MCP specifically: no paid plan is needed to connect, though some actions vary by plan.
Cancelling yes, rescheduling no. Calendly's developer FAQ states that an event is cancelled with a POST request to the cancel event endpoint, and that no API endpoint supports rescheduling an event or invitee. Reschedule and cancel URLs are published on the invitee resource and in webhook payloads instead, so an assistant can retrieve and pass on the link but cannot move the meeting itself.
Yes. Calendly's developer FAQ states that the Scheduling API books meetings directly from apps, workflows or AI assistants. The MCP tool behind it is meetings-create_invitee, which Calendly's supported-tools table maps to POST /invitees and marks as requiring a paid Calendly plan. Its AI agents guide adds that invitation emails and texts fire from the event type's own notification settings.
Ninety days. Calendly's developer FAQ states that single-use scheduling links which have not been used to book an event expire after 90 days. The connector creates them two ways: scheduling_links-create_single_use_scheduling_link makes an uncustomised link, and shares-create_share makes a customised one from an existing event type.
Yes. Calendly's developer FAQ states that an event type's availability is updated by calling the Update Event Type Availability Schedules endpoint. Two tools cover this: event_types-update_event_type_availability_schedule writes the schedule, and availability-list_user_availability_schedules and availability-list_user_busy_times read it. Calendly's own example prompt is removing Fridays from a coaching session's available days.
Three account changes revoke tokens automatically. Calendly's developer FAQ states that both OAuth and personal access tokens are revoked if the account's login email, password or login method is changed. Tokens can also be revoked manually — OAuth tokens through the revoke token endpoint. Any of these ends the assistant's access immediately, so a password reset disconnects the connector.
No. Calendly's AI help centre article states plainly that Calendly does not sell customer data or use it to train AI models, and that no third-party AI provider is allowed to train on your data. It adds that data you submit and responses you receive serve only your own experience and are not shared between customers. Calendly names OpenAI as its current LLM provider for AI features.
:write scope implicitly includes the matching :read · retrieved 2026-08-18https://mcp.calendly.com/ — an anonymous initialize returnshttps://calendly.com/.well-known/oauth-authorization-server returns HTTP 200 with registration_endpoint: "https://calendly.com/oauth/register", code_challenge_methods_supported: ["S256"] and token_endpoint_auth_methods_supported: ["none"], and no scopes_supported key. The same path on mcp.calendly.com returns HTTP 404. Our own observation, 2026-08-18. · retrieved 2026-08-18partner tier, the productivity category, the streamable-HTTP transport, the https://mcp.calendly.com/ endpoint and the "Read and write" permission label, from our committed snapshot dated 2026-08-16 · retrieved 2026-08-16developer.calendly.com/robots.txt (retrieved 2026-08-18) allows all paths, names the sitemap we used to resolve every page URL above without guessing, and carries no Content-Signal directives. calendly.com/robots.txt allows /help/ and /blog/ while disallowing /app/ and query strings, and likewise carries no Content-Signal directives. Neither host serves a usable llms.txt on the developer domain — developer.calendly.com/llms.txt returns the Gatsby 404 SPA shell with HTTP 200, as does appending .md to any page URL. · retrieved 2026-08-18Connect Calendly once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.