📅 MCP Server Configuration - Calendly

No. Available MCP Calendly tools only allow to READ data (availability, events, invitees) and CANCEL events. Actual booking must occur via the public Calendly link or other systems. The assistant can however verify availability and provide the correct link to the customer.

Login to your Calendly account, go to Settings > Integrations > API & Webhooks. Generate a new Personal Access Token and copy it. This token must be inserted in the "Authentication Token" field in AI4CALL configuration. The token always starts with "eyJ".

The assistant can: verify time availability (calendly_get_available_times), consult scheduled events (calendly_get_scheduled_events), read invitee details (calendly_get_event_invitees and calendly_get_invitee), retrieve available event types (calendly_get_event_types), and cancel events (calendly_cancel_event). Cannot create new appointments.

calendly_get_event_invitees returns ALL invitees of a specific event (complete list). calendly_get_invitee returns details of ONE SINGLE specific invitee via their UUID. Use the first to see who participates in an event, the second to retrieve detailed data of a specific person.

Yes, the operation is IRREVERSIBLE. Once the event is cancelled via the MCP server, it cannot be restored. Therefore it is fundamental to instruct the assistant to ALWAYS ask explicit customer confirmation before executing cancellation.

It must first invoke calendly_get_event_types to retrieve all event types configured on your Calendly (e.g. "Consultation 30min", "Videocall 1h"). Then uses the UUID of the correct event type to call calendly_get_available_times. In the prompt you can specify exact names or let the assistant identify the right type from the request.

Not at MCP tool level - if you activate calendly_cancel_event, it works on all events. Limitation must be managed at prompt level: instruct the assistant to cancel only events matching specific criteria (e.g. only future events, only for certain customers, only with explicit confirmation).

The assistant uses calendly_get_event_invitees or calendly_get_invitee to retrieve the confirmation URL from the event. Then, if you configured WhatsApp Business or Email SMTP tool, it can invoke send_whatsapp_message or send_email to automatically send the link to the customer during the call.

Yes. calendly_get_event_invitees returns ALL invitees of an event, so it also works for group events. You can see how many people confirmed, their data, and each invitee status (active, cancelled, pending).

All MCP tools will stop working immediately. The assistant will receive authentication errors when trying to invoke any Calendly tool. You will need to generate a new token from Calendly settings and update it in AI4CALL configuration.

No. You can configure only one Bearer Token at a time in the MCP server. If you have multiple Calendly accounts, you must choose which account to link. To manage multiple accounts, you should configure separate AI4CALL assistants, each with its own token.

It must first invoke calendly_get_scheduled_events to retrieve all scheduled events, then identify the correct one comparing date/time or details provided by customer. Once found the correct event UUID, it can invoke calendly_cancel_event to cancel it.

Shows ONLY slots actually available for booking, based on calendars linked to your Calendly. Already occupied times, slots outside business hours, or blocked dates are not shown. It's the same availability a customer would see on the public Calendly link.

No. The Calendly API via MCP does not support direct event modification (reschedule). You can only cancel the existing event and have the customer book a new slot. The assistant can guide the customer in this sequential process.

Retrieves information about the Calendly account authenticated via token: name, email, timezone, profile URL, and organization UUID. Useful to verify connection works and to retrieve data needed by other tools (some require user URI).

Yes. In the prompt instruct the assistant to invoke calendly_get_available_times with start_time set to current date/time. The tool will return available slots in chronological order, and the assistant can propose first 3-5 slots to the customer.

For each invitee: full name, email, status (active/canceled), timezone, invitation creation date, confirmation URL, any custom questions/answers, and unique invitee UUID. All data necessary to contact customer or verify booking status.

Yes, but limits depend on your Calendly plan. If the assistant makes too many requests in short time, Calendly API may temporarily block calls. For high traffic events, optimize prompt to reduce unnecessary calls (e.g. cache availability for a few minutes).

Yes. The assistant can use multiple MCP tools simultaneously. Example workflow: use Calendly to verify availability, then use WhatsApp tool to send confirmation, or use Google Calendar MCP to synchronize event. MCP tools are composable and LLM orchestrates them autonomously.

Calendly automatically manages time zones. calendly_get_available_times accepts start_time parameter in ISO 8601 format with timezone. Events and invitees returned always include specific timezone. Assistant can automatically convert if needed, using customer timezone.