Connect Ondes PRO to Windsurf

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. 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. 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.

   jsonCopy

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

3. 3

   Refresh the server list

   Save the file and refresh the MCP panel: the ondes server appears, waiting for authorisation.

4. 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. 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.

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

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

Eight tools, not 135: why it matters in Windsurf

Example: a stock dashboard for the workshop

Thomas is building a small internal screen for Atelier Lumen that lists the parts to reorder. He asks Cascade to work from the real data.

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.

Going further

• Inventory managementStock levels, deliveries, bills of materials and production orders read and prepared by your assistant.Read
• Build an integrationScoped keys, signed webhooks, idempotency and test mode for a back office that never creates duplicates.Read
• MCP vs REST APIWhat really sets them apart, when to pick which, and why at Ondes PRO they work together.Read
• MCP server securityOAuth 2.1, short-lived tokens, instant revocation and write safeguards: what your IT team needs to know.Read

Frequently asked questions

Read next

• ClaudeClaude Desktop, claude.ai and Claude Code: one custom connector, one OAuth sign-in, and you are set.Read
• CursorOne `.cursor/mcp.json` file, one OAuth sign-in: Cursor’s agent codes against your real workspace.Read
• Visual Studio CodeGitHub Copilot agent mode reads and calls your workspace from `.vscode/mcp.json`.Read
• ChatGPTChatGPT developer mode accepts your workspace as an MCP connector, over OAuth.Read
• ZedThree lines under `context_servers`, and Zed handles the OAuth sign-in on its own.Read
• ClineThe open-source Cline agent connects over `streamableHttp` and lets you approve each tool.Read