# Connect Ondes PRO to Claude

> Add Ondes PRO as a custom connector in Claude or Claude Code: one-click OAuth, copy-ready configuration, concrete examples. Tested by our team.

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

Claude connects to your Ondes PRO workspace’s MCP server as a **custom connector** — in the desktop app, on claude.ai, or in the terminal with Claude Code. It takes a minute, with no key to copy: the connection uses OAuth.

## Add Ondes PRO to Claude Desktop or claude.ai

Custom connectors are available on every Claude plan (the free plan allows one). Anthropic still labels them beta, so exact menu names may change.

1. **Find your workspace address** — It is your Ondes PRO admin address followed by `/mcp/`. Type your subdomain in the field at the top of the page: every configuration adapts.

```
https://your-workspace.ondes.pro/mcp/
```
2. **Open connectors** — In Claude, open **Customize**, then **Connectors**, then **+ Add** and **Add custom connector**. In a Team or Enterprise organisation, an admin adds it once from the organisation settings.
3. **Paste the address and confirm** — Name the connector “Ondes PRO” and paste the address. Leave the advanced OAuth settings empty: the server announces itself.
4. **Authorise the connection** — A window from your Ondes PRO workspace opens. Sign in, read the consent screen — it states plainly what the connection will allow — then authorise. Claude then lists the server’s tools.
5. **Ask your first question** — Try “Which invoices are overdue?” or “Summarise this week’s store activity”. Claude picks the tools to call on its own.

![Ondes PRO consent screen (in French): destination, callback address, name declared by the application, account, and a warning about the connection’s full permissions.](https://ondes.pro/integrations/mcp-consentement-oauth.webp)

## With Claude Code, in the terminal

For a developer building an integration, Claude Code is the most direct path: it reads your workspace’s documentation while it writes the code. Then type `/mcp` inside Claude Code and pick “ondes” to sign in.

Where to set it up : One terminal command, then `/mcp` inside Claude Code to sign in.

**OAuth connection (recommended)** (Terminal)

```bash
claude mcp add --transport http ondes https://your-workspace.ondes.pro/mcp/
```

**API key connection** (Terminal)

```bash
claude mcp add --transport http ondes https://your-workspace.ondes.pro/mcp/ \
  --header "Authorization: ApiKey opk_…"
```

_Tested by our team. Vendor documentation : https://code.claude.com/docs/en/mcp_

## OAuth or API key: which one?

**OAuth** is the default: nothing to copy, nothing to store, and the connection shows up in your workspace under the machine’s name, revocable in one click. It acts with your full permissions.

An **API key** suits cases where you want to narrow access — say, a read-only invoicing key for a colleague building dashboards. Create it in **API & Developers → API keys**; it is shown only once. A key never exceeds its holder’s permissions. Both options are detailed on the [MCP server security](https://ondes.pro/en/integrations/mcp/security) page.

## What a conversation looks like

_Example conversation · demo data (Atelier Lumen)_

> **You** : Which invoices are overdue, and by how much?
>
> 🔧 `ondes_ressource` Reads the `billing/factures` sheet to learn the available filters.
>
> 🔧 `ondes_appeler` `GET billing/factures?statut=en_attente` — 3 invoices whose `etat` is `en_retard`.
>
> **Assistant** : Three invoices are overdue, totalling **€4,860 incl. VAT**: Brasserie La Canopée (FAC-2026-0187, 18 days), Studio Nord (FAC-2026-0191, 9 days) and Galerie Ressac (FAC-2026-0196, 3 days). Shall I draft a reminder for the two oldest?

## Request ideas

- “Create a card in the Workshop board for Hôtel Ker Aven’s order, due Friday.”
- “How many Arc floor lamps are left in stock, and when should production restart?”
- “Set up a 15% promo code valid until Sunday for the newsletter.”
- “List unread emails in contact@ that mention a quote.”
- “Schedule a video call with Studio Nord on Tuesday at 10am and send the invitation.”

> **If Claude cannot see your modules** — The connection follows your role: a module your role does not open stays invisible to Claude. Connecting also requires the **API & Developers** permission. If a tool is missing, ask your workspace admin to adjust your role, then reconnect the connector.

## Other assistants

- [ChatGPT](https://ondes.pro/en/integrations/mcp/clients/chatgpt) — ChatGPT developer mode accepts your workspace as an MCP connector, over OAuth.
- [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.
- [Visual Studio Code](https://ondes.pro/en/integrations/mcp/clients/visual-studio-code) — GitHub Copilot agent mode reads and calls your workspace from `.vscode/mcp.json`.
- [Windsurf](https://ondes.pro/en/integrations/mcp/clients/windsurf) — Cascade plugs into your workspace through `mcp_config.json` and the `serverUrl` key.

## Frequently asked questions

### Is Claude’s free plan enough?

Yes, to try it: it allows one custom connector. Paid Claude plans accept more and give more usage.

### Can Claude change my data without asking?

Claude asks for your approval before using a tool that writes, depending on your permission settings in Claude. On the Ondes PRO side, writes go to test mode when the resource has one, and the built-in assistant proposes its changes as a plan to confirm.

### How do I disconnect Claude?

In your workspace, under the **MCP** tab of **API & Developers**: every connection is listed per machine with its last activity, and “Revoke” cuts it off immediately. You can also remove the connector in Claude.

### Do Claude Code and Claude Desktop share the same connection?

No: each app authorises separately and appears as its own connection in your workspace. That is intentional — you can revoke one without touching the other.