# Ondes PRO Calendar: a schedule your AI can keep > Connect Claude, ChatGPT or Cursor to Ondes PRO’s calendar over MCP: appointments, recurring meetings, reminders, moving one occurrence. With your permissions. Updated on 2026-10-21 · The Ondes PRO team · https://ondes.pro/en/integrations/mcp/modules/calendar **Ondes PRO’s calendar** opens up to your AI assistant through your workspace’s **MCP server**. Claude, ChatGPT, Cursor or Visual Studio Code can check the schedule, book an appointment with attendees and a location, set up a **recurring meeting** with reminders, or move a single occurrence of a series without touching the rest. Everything happens with your permissions, in the calendar your team already uses. ## Set up the weekly workshop stand-up, then move one _Example conversation · demo data (Atelier Lumen)_ > **You** : Create a “Workshop stand-up” every Monday at 9am, 30 minutes, until the end of December, with Hugo, Inès and Jules. Remind us 15 minutes before, by email too. > > 🔧 `ondes_ressource` Reads the `agenda/evenements` sheet: start, end, attendees, repeat rule, reminders. > > 🔧 `ondes_appeler` `POST agenda/evenements` with `simuler: true` — the series is valid: 10 occurrences from 26 October to 28 December. > > **Assistant** : The series covers **10 Mondays**, from 26 October to 28 December, 9:00 to 9:30, with Hugo Lambert, Inès Roche and Jules Perrin. Reminder 15 minutes before, in the app and by email. Save it? > > **You** : Yes. And move the 9 November one to Tuesday the 10th, same time. > > 🔧 `ondes_appeler` Series created. Moving a single occurrence is handed to `ondes_assistant`. > > 🔧 `ondes_assistant` Plan proposed: move the 9 November occurrence to 10 November, 9am; the other Mondays stay as they are. > > **Assistant** : Ondes PRO’s assistant suggests detaching **only** the 9 November occurrence and placing it on Tuesday the 10th at 9am. The other nine Mondays do not move. Shall I confirm? > > **You** : Confirm. > > **Assistant** : Done. Hugo, Inès and Jules have the series in their calendars, with Tuesday 10 November in place of Monday the 9th. ## What can an AI do with a calendar over MCP? Hooking a **calendar up to an MCP server** lets the assistant answer “what’s on tomorrow?” from the real schedule, then act on it: book a client appointment with a location and notes, invite colleagues, pick a colour, set one or more reminders, or link the event to a Kanban card so the job and its time slot stay connected. Appointments are not cut off from the rest of the business. In Ondes PRO, the calendar view brings together calendar events, Kanban card due dates and video meetings, so an assistant planning the week sees Friday’s delivery and Tuesday’s meeting in one place. For the online meeting room itself, see [video conferencing over MCP](https://ondes.pro/en/integrations/mcp/modules/video-conferencing). ## Recurring meetings: one rule, not fifty-two rows An “every Monday” series is **a single event** carrying its repeat rule: frequency, interval, weekdays, end date or number of occurrences. Occurrences are worked out when the calendar is read, on Paris wall-clock time — 9am stays 9am after the clocks change. A month without the requested day (a 31st) is simply skipped. Changing a series means saying **how far** the change goes: this occurrence only, this one and the following ones, or the whole series. Ondes PRO’s built-in assistant (`ondes_assistant`) handles that: it proposes the change as a plan, and nothing moves until you approve. A moved occurrence becomes its own entry, and its original date drops out of the series. ## What the assistant uses to manage the schedule Two MCP server tools share the work, depending on the request. | Need | Tool and resource | Behaviour | | --- | --- | --- | | Read or create an event | `ondes_appeler` on `agenda/evenements` | Direct API call, dry-runnable with `simuler: true`. | | Know the fields | `ondes_ressource` on `agenda/evenements` | Exact sheet: required fields, filters, ordering. | | Move one occurrence of a series | `ondes_assistant` | Plan proposed, run after `confirmer`. | | “What do I have this week?” | `ondes_assistant` | Series occurrences expanded, due dates included. | | Hear about changes | Signed webhooks | Lifecycle events: created, updated, deleted. | ## Appointment reminders, set by the AI The assistant can put up to five reminders on an event. Here is what Ondes PRO does with them. - **In the app and on the phone**: every attendee and the organiser get the reminder, provided they have access to the calendar. - **By email** when that option is ticked on the event. - **Once per occurrence**: a weekly series rings every week, never twice for the same slot. Moving an appointment re-arms its reminders for the new time. - **No late surprises**: creating a 10am appointment at 9:50 with a “1 hour before” reminder does not fire after the fact. - **All-day events**: the reminder counts from 9am that day. > **An invitation is still an invitation** — Adding an attendee to an event notifies them — that is the point of a shared calendar. Before letting the assistant invite a whole team, ask for a dry run (`simuler: true`): it shows the exact attendee list and the computed series, without saving or sending anything. ## For developers: showing the Ondes PRO calendar elsewhere Want to show showroom slots on a website, or feed an internal tool? Your coding assistant reads the `agenda/evenements` sheet with `ondes_ressource`, checks `ondes_impossible` for what the API does not do, then writes the client. A webhook subscription notifies your service whenever an event is created, updated or deleted, so it never has to poll the API. For an unattended script, create an **API key** scoped to the calendar — read-only if your service only displays events. The [integration guide](https://ondes.pro/en/integrations/mcp/guides/build-an-integration) and the [MCP server security page](https://ondes.pro/en/integrations/mcp/security) explain how a scoped key differs from an OAuth connection. ## Keep exploring - [Video conferencing](https://ondes.pro/en/integrations/mcp/modules/video-conferencing) — Your AI assistant opens a meeting room, invites the right people and hands you the embed code. - [Kanban](https://ondes.pro/en/integrations/mcp/modules/kanban) — Your AI assistant creates, moves and comments on cards, and your teammates see it happen live. - [ChatGPT](https://ondes.pro/en/integrations/mcp/clients/chatgpt) — ChatGPT developer mode accepts your workspace as an MCP connector, over OAuth. - [Automate with AI](https://ondes.pro/en/integrations/mcp/guides/automate-with-ai) — Reminders, reports and automations described in one sentence, always reviewed before anything runs. ## Frequently asked questions ### Can an MCP server connect to a business calendar? Yes. Ondes PRO’s calendar is one of the modules exposed by each workspace’s MCP server. A compatible assistant reads events, creates them, invites colleagues and sets reminders, within the connected person’s permissions. ### Can the AI handle recurring meetings? Yes. A series is a single event carrying its rule (frequency, weekdays, end). To change one occurrence, or this one and the following ones, Ondes PRO’s built-in assistant proposes a plan that runs once you approve; the other occurrences stay put. ### Do reminders reach my phone? Yes. Reminders go out in the web app, as notifications in the Ondes PRO mobile app, and by email when the option is on for the event. Up to five reminders per event, each sent once per occurrence. ### Do my appointments shift when the clocks change? No. Series are computed on Paris wall-clock time: a 9am appointment is still at 9am after the change. ### Is calendar access over MCP included in my plan? Yes. The calendar and the MCP server are included in every Ondes PRO plan, with nothing extra to enable. See [pricing](https://ondes.pro/en/pricing).