# Connect Ondes PRO to Windsurf

> Add the Ondes PRO MCP server to Windsurf: mcp_config.json with the serverUrl key, OAuth sign-in, and Cascade coding against your workspace’s real documentation.

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

In Windsurf, MCP servers are used by **Cascade**, the editor’s agent. Declare your Ondes PRO workspace in `mcp_config.json` and Cascade gets eight tools to understand your API, validate its requests and query your data — a small, fixed set that does not clutter its tool list.

## Add Ondes PRO to Cascade’s MCP servers

Windsurf’s quirk fits in one word: a remote server’s address goes under the `serverUrl` key, not `url` as elsewhere. Fix that first if you are pasting another editor’s configuration.

1. **Open Cascade’s MCP panel** — In the Cascade panel, open MCP server management, then the option to edit the raw configuration. Windsurf opens its `mcp_config.json` file, stored in your home folder (under `~/.codeium/windsurf/` in current versions).
2. **Declare the server with serverUrl** — Add an `ondes` entry under `mcpServers`. Type your subdomain at the top of the page so the address is right.

```json
{
  "mcpServers": {
    "ondes": { "serverUrl": "https://your-workspace.ondes.pro/mcp/" }
  }
}
```
3. **Refresh the server list** — Save the file and refresh the MCP panel: the `ondes` server appears, waiting for authorisation.
4. **Authorise the connection in your workspace** — A window from your Ondes PRO workspace opens. Sign in and approve the consent screen, which states plainly what the connection will allow. The eight tools become available to Cascade.
5. **Ask Cascade** — For example: “Which API resource handles stock movements, and which fields does it require?”. Cascade picks the tools and shows every call.

## Copy-ready mcp_config.json

The file is personal and does not live in your repository, so the API key form is less exposed than elsewhere. Still, prefer OAuth, which leaves no secret on disk.

Where to set it up : Windsurf’s `mcp_config.json` file (Cascade MCP panel → Configure).

**OAuth connection (recommended)** (mcp_config.json)

```json
{
  "mcpServers": {
    "ondes": {
      "serverUrl": "https://your-workspace.ondes.pro/mcp/"
    }
  }
}
```

**API key connection** (mcp_config.json)

```json
{
  "mcpServers": {
    "ondes": {
      "serverUrl": "https://your-workspace.ondes.pro/mcp/",
      "headers": {
        "Authorization": "ApiKey opk_…"
      }
    }
  }
}
```

_Standard MCP compatible. Vendor documentation : https://docs.devin.ai/desktop/cascade/mcp_

## Eight tools, not 135: why it matters in Windsurf

Windsurf caps the total number of tools Cascade can have enabled across all servers. A server that exposed every API resource as its own tool — the Ondes PRO v1 API has around 135, each with several verbs — would hit that cap on its own, and the tool definitions would sit in context permanently.

The Ondes PRO server does the opposite: **eight fixed tools**, about 2,700 tokens of permanent context, and all the depth behind them. Cascade discovers resources with `ondes_chercher` and `ondes_ressource` when it needs them, and calls any of them through `ondes_appeler`. You keep room for your other MCP servers.

## Example: a stock dashboard for the workshop

_Example conversation · demo data (Atelier Lumen)_

> **You** : Create a `stock.tsx` page listing components below their alert threshold, most urgent first. Only load the columns we need.
>
> 🔧 `ondes_ressource` `inventory/composants` sheet: stock and threshold fields, available filters and ordering.
>
> 🔧 `ondes_guide` Pagination section: cursor recommended for long lists, `fields` and `page_size` parameters.
>
> 🔧 `ondes_appeler` `GET inventory/composants` with narrowed `fields` — 212 components, cursor-paginated response.
>
> **Assistant** : The page is ready. It only requests reference, name, stock and threshold, and follows the cursor to the end. On your current data, 9 components are below threshold; the most urgent is the brass E27 lamp holder used by the Suspension Laiton and the Arc floor lamp. Want me to add a link to each affected product’s bill of materials?

## What Cascade gains with Ondes PRO

- Documentation that is **current by design**: generated from your workspace’s real routes on every call, not copied once and forgotten.
- Documentation **sized to you**: Cascade only sees the modules your role opens.
- Complete recipes, verified against the API, through `ondes_exemple`: reading without N+1 calls, invoicing, subscribing to events.
- Careful writes: a dry run on any resource, test mode by default when the resource has a test twin, and the mode always stated in the response.

> **Windsurf in a team** — In a Windsurf team, an admin can restrict which MCP servers are allowed. If the `ondes` server stays greyed out, ask for it to be added to the list. On the Ondes PRO side, each developer authorises with their own account: the connection shows up under their name and machine in the workspace’s **MCP** tab, revocable on its own.

## Going further

- [Inventory management](https://ondes.pro/en/integrations/mcp/modules/inventory) — Stock levels, deliveries, bills of materials and production orders read and prepared 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.
- [MCP vs REST API](https://ondes.pro/en/integrations/mcp/mcp-vs-rest-api) — What really sets them apart, when to pick which, and why at Ondes PRO they work together.
- [MCP server security](https://ondes.pro/en/integrations/mcp/security) — OAuth 2.1, short-lived tokens, instant revocation and write safeguards: what your IT team needs to know.

## Frequently asked questions

### How do I add a remote MCP server to Windsurf?

From Cascade’s MCP panel, open the raw `mcp_config.json` configuration and declare the server under `mcpServers` with the `serverUrl` key. For Ondes PRO: `https://<your-workspace>.ondes.pro/mcp/`, then refresh and authorise the connection.

### Why doesn’t Windsurf find my server declared with url?

For a remote server, Windsurf documents the `serverUrl` key. A configuration copied from Cursor or Zed, which use `url`, needs that key renamed.

### Does the Ondes PRO server use up many tools in Windsurf?

No: it exposes eight, always the same ones, for about 2,700 tokens of permanent context. The API’s 135 or so resources are discovered and called through those eight tools.

### Can Cascade write to my workspace without me noticing?

Every tool call is shown in Cascade, and writes only ever use your permissions. On the Ondes PRO side, the response always states whether a write was real, in test mode or simulated, and every MCP call is logged in your workspace.

### Has the Ondes PRO team tested Windsurf?

No. Cascade reaches remote servers through the standard MCP protocol our server implements, so with the `serverUrl` key the connection should work. Only Claude has been verified end to end by our team, and Windsurf’s MCP panel sometimes moves around.