# Ondes PRO Video: online meetings your AI can set up

> With Ondes PRO’s MCP server, your AI creates a video meeting room, invites colleagues and clients, and returns the iframe to embed. Test mode by default.

Updated on 2026-10-21 · The Ondes PRO team · https://ondes.pro/en/integrations/mcp/modules/video-conferencing

**Ondes PRO’s video conferencing** can be driven from your AI assistant through your workspace’s **MCP server**. Claude, ChatGPT, Cursor or Visual Studio Code create a meeting room, invite colleagues and clients from your CRM, turn on a waiting room and fetch the `<iframe>` block ready to paste into a website. By default, the first room the assistant creates is a **test room**: it exists, but nobody is invited.

## Demo a prototype to a client, without a stray invitation

_Example conversation · demo data (Atelier Lumen)_

> **You** : Set up a video call on Thursday at 2pm with Galerie Ressac to show the Tripod lamp prototype. Invite Thomas, and use a waiting room.
>
> 🔧 `ondes_ressource` Reads the `visio/reunions` sheet: internal attendees, CRM clients, waiting room, test twin.
>
> 🔧 `ondes_appeler` `GET crm/fiches?search=Ressac` — record found, main contact with an email address.
>
> 🔧 `ondes_appeler` `POST visio/reunions` in **test mode** — test room created, `embed.iframe` returned, no invitation sent.
>
> **Assistant** : I set the meeting up in test mode: **Thursday 2–3pm**, “Tripod lamp prototype”, waiting room on, with Thomas Girard and Galerie Ressac’s contact invited by email. Nobody has been notified yet. Create it for real?
>
> **You** : Yes, send it.
>
> 🔧 `ondes_appeler` `POST visio/reunions` with `reel: true` — real meeting created, invitations sent.
>
> **Assistant** : Sent. Thomas has the invitation in Ondes PRO, Galerie Ressac received it by email, and the meeting shows in your calendar. External guests will wait in the waiting room until you let them in.

## Creating a video meeting with an AI: how does it work?

Your assistant talks to the MCP server, which calls the `visio/reunions` resource of the Ondes PRO API under your identity. A meeting has a title, a description, a time slot, internal attendees and, if you like, CRM clients invited by email. The response comes back straight away with the room link and the embed block.

Because video lives in the same software as the calendar and the CRM, the assistant copies nothing by hand: it finds Galerie Ressac’s contact in the CRM, books the meeting, and it lands in everyone’s calendar. See also [the calendar over MCP](https://ondes.pro/en/integrations/mcp/modules/calendar) and [the CRM over MCP](https://ondes.pro/en/integrations/mcp/modules/crm).

## Test mode: check a meeting before bothering anyone

The `visio/reunions` resource has a **test twin**. When your assistant creates a meeting without explicitly asking for the real thing, the write goes to that sandbox: the room exists, its `<iframe>` is returned and the integration can be checked end to end — but **nobody is invited**. The `ondes_appeler` tool picks this mode by default, and every response states which mode was used.

To send real invitations, the assistant repeats the call with `reel: true`, which it normally does only after you agree. On the API side, test and real meetings never mix: each mode only sees its own. The [MCP server security page](https://ondes.pro/en/integrations/mcp/security) lays out all of these safeguards.

## What your assistant can set on a meeting

- **The time slot**: scheduled start and end, or an instant meeting.
- **Internal attendees**: team members only; an outside identifier is rejected, because the list triggers invitations.
- **CRM clients**: invited by email, provided the connection can access clients.
- **The waiting room**: external guests wait until you admit them.
- **Sites allowed to show the room**: declared origins for `<iframe>` embedding.
- **Closing**: deleting a meeting through the API closes the room without erasing its history.

## For developers: embedding a video room in your website

The most common developer use case is showing an Ondes PRO room inside a client portal or a booking page. The response to a `POST visio/reunions` already contains the full `<iframe>` block, `allow="camera; microphone"` attribute included: leaving it out is what silences camera and microphone with no useful error, hence the choice.

The room only renders on the origins you declare, enforced by a `frame-ancestors` policy rather than a blanket ban on framing. The `lien-embed/` and `revoquer-liens/` actions regenerate or invalidate links already handed out. Ask your coding assistant for the matching recipe with `ondes_exemple`, then try everything in test mode before going live.

## What the assistant sends

A typical call made through `ondes_appeler`. Test mode applies until `reel` is requested.

```json
{
  "methode": "POST",
  "chemin": "visio/reunions",
  "corps": {
    "title": "Tripod lamp prototype",
    "scheduled_start": "2026-10-29T14:00:00+01:00",
    "scheduled_end": "2026-10-29T15:00:00+01:00",
    "waiting_room_enabled": true
  }
}
```

`methode`, `chemin` and `corps` are the tool’s real arguments. Without `reel: true`, this write creates a test room.

> **You can join a room without managing it** — With several companies, the meeting list is partitioned: a subsidiary only manages its own. But someone invited to a sister company’s meeting can still join it — a call brings people together, not org charts. Your assistant inherits exactly these rules.

## Keep exploring

- [Calendar](https://ondes.pro/en/integrations/mcp/modules/calendar) — Your AI assistant books appointments, handles recurring series and sets reminders for the team.
- [CRM](https://ondes.pro/en/integrations/mcp/modules/crm) — Customer records, follow-up notes, pipeline and reminders kept up to date by your assistant.
- [Build an integration](https://ondes.pro/en/integrations/mcp/guides/build-an-integration) — Scoped keys, signed webhooks, idempotency and test mode for a back office that never creates duplicates.
- [Cursor](https://ondes.pro/en/integrations/mcp/clients/cursor) — One `.cursor/mcp.json` file, one OAuth sign-in: Cursor’s agent codes against your real workspace.

## Frequently asked questions

### Can an AI create a video meeting?

Yes. With Ondes PRO, an MCP-compatible assistant creates a meeting through the `visio/reunions` resource: time slot, internal attendees, CRM clients invited by email, waiting room. The response includes the room link and the embed block.

### What if the AI picks the wrong attendees?

By default the meeting is created in test mode: the room exists but nobody is invited. Invitations only go out with a real call, which the assistant normally makes after you approve. A meeting can then be closed without losing its history.

### Can I embed the meeting room in my own website?

Yes. The creation response contains a ready-to-paste `<iframe>` with camera and microphone permissions. It only renders on the origins you declare, and links already shared can be revoked at any time.

### Do my clients need an account to join?

No. A CRM client receives an email invitation and joins from the link. With the waiting room on, they wait until a team member lets them in.

### Is video conferencing over MCP included?

Yes. Video conferencing and the MCP server are included in every Ondes PRO plan. See [pricing](https://ondes.pro/en/pricing).