# MCP clients that connect to Ondes PRO

> Claude, Cursor, VS Code, ChatGPT, Windsurf, Zed, Cline or JetBrains: compare the MCP clients that connect to Ondes PRO, via OAuth or an API key.

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

Your workspace’s MCP server speaks the standard protocol over HTTP (“Streamable HTTP”). Any **MCP client** that can reach a remote server can plug into it: a chat assistant such as Claude or ChatGPT, a code editor such as Cursor, Visual Studio Code, Windsurf, Zed or a JetBrains IDE, or an extension such as Cline. This comparison shows how each one connects and where you configure it.

## MCP clients for Ondes PRO, side by side

The OAuth column tells you whether the client handles authorisation on its own: it opens a window from your workspace, you sign in, and there is no key to copy. Otherwise, an API key created under **API & Developers** does the job.

| Client | OAuth sign-in | Where to configure it | Status |
| --- | --- | --- | --- |
| [Claude Desktop, claude.ai, Claude Code](https://ondes.pro/en/integrations/mcp/clients/claude) | Yes | Customize → Connectors, or `claude mcp add` in the terminal | Tested by our team |
| [Cursor](https://ondes.pro/en/integrations/mcp/clients/cursor) | Yes | `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (machine) | Standard MCP compatible |
| [Visual Studio Code](https://ondes.pro/en/integrations/mcp/clients/visual-studio-code) | Yes | `.vscode/mcp.json`, GitHub Copilot agent mode | Standard MCP compatible |
| [ChatGPT](https://ondes.pro/en/integrations/mcp/clients/chatgpt) | Yes | Settings → Connectors, developer mode (beta, web) | Standard MCP compatible |
| [Windsurf](https://ondes.pro/en/integrations/mcp/clients/windsurf) | Yes | `mcp_config.json`, `serverUrl` key | Standard MCP compatible |
| [Zed](https://ondes.pro/en/integrations/mcp/clients/zed) | Yes | `context_servers` key in settings | Standard MCP compatible |
| [Cline](https://ondes.pro/en/integrations/mcp/clients/cline) | Yes | `cline_mcp_settings.json`, `type: streamableHttp` | Standard MCP compatible |
| [JetBrains AI Assistant](https://ondes.pro/en/integrations/mcp/clients/jetbrains) | Not documented by JetBrains | Settings → Tools → AI Assistant → MCP | Standard MCP compatible |

“Tested” means our team verified the connection end to end against a real instance. “Standard MCP compatible” means the client implements the protocol our server follows: the connection should work, but the client’s interface may change without notice. Formats checked on 21 October 2026 against each vendor’s documentation.

## Which MCP client should you use to run your business?

If you run the business — orders, quotes, payment reminders, scheduling — a **chat assistant** feels most natural. [Claude](https://ondes.pro/en/integrations/mcp/clients/claude) is the only client our team has tested and connects in a few clicks; [ChatGPT](https://ondes.pro/en/integrations/mcp/clients/chatgpt) works through developer mode, with write access that depends on your ChatGPT plan.

If you are **building** an integration — your storefront, a dashboard, an in-house connector — stick with the editor you already use. Your coding assistant then reads your own workspace’s documentation as it writes: the exact fields of your resources, the filters, the test twin. It no longer has to guess a URL.

Whatever the client, the connection carries **your permissions and nothing more**. A module your role does not open stays invisible to the assistant.

## Chat assistants

- [Claude](https://ondes.pro/en/integrations/mcp/clients/claude) — Claude Desktop, claude.ai and Claude Code: one custom connector, one OAuth sign-in, and you are set.
- [ChatGPT](https://ondes.pro/en/integrations/mcp/clients/chatgpt) — ChatGPT developer mode accepts your workspace as an MCP connector, over OAuth.

## Code editors and extensions

- [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.
- [Zed](https://ondes.pro/en/integrations/mcp/clients/zed) — Three lines under `context_servers`, and Zed handles the OAuth sign-in on its own.
- [Cline](https://ondes.pro/en/integrations/mcp/clients/cline) — The open-source Cline agent connects over `streamableHttp` and lets you approve each tool.
- [JetBrains](https://ondes.pro/en/integrations/mcp/clients/jetbrains) — AI Assistant in JetBrains IDEs plugs into your workspace through its MCP setting.

## Another MCP client? The generic configuration

Your tool is not listed — Gemini CLI, for instance, takes a URL under an `httpUrl` key? Any client that can reach a remote MCP server over HTTP can connect. Rename the keys to match its documentation; the address and the header stay the same.

Where to set it up : Any client that speaks MCP over HTTP (“Streamable HTTP” transport).

**OAuth connection (recommended)** (Configuration)

```json
{
  "mcpServers": {
    "ondes": {
      "type": "http",
      "url": "https://your-workspace.ondes.pro/mcp/"
    }
  }
}
```

**API key connection** (Configuration)

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

_Standard MCP compatible. Vendor documentation : https://modelcontextprotocol.io/specification_

> **One connection per machine, revocable any time** — Every client authorised through OAuth shows up in the **MCP** tab of **API & Developers**, named after the machine (“Cursor, on my laptop”), with its last activity. “Revoke” cuts access immediately, without waiting for the one-hour token to expire. Details on the [MCP server security](https://ondes.pro/en/integrations/mcp/security) page.

## Frequently asked questions

### Can several MCP clients connect to the same Ondes PRO workspace?

Yes. Each client authorises separately and appears as its own connection in your workspace’s MCP tab. You can use Claude for operations and Cursor for code, and revoke one without affecting the other.

### What is the difference between “Tested” and “Standard MCP compatible”?

Only Claude has been verified end to end by our team against a real instance. The other clients implement the MCP protocol our server follows: the connection should work, but we do not control their interface, which may change.

### Is the MCP server part of my subscription?

Yes, it is included in every Ondes PRO plan, Essentiel included. There is nothing to switch on: the address `https://<your-workspace>.ondes.pro/mcp/` exists as soon as the workspace is created.

### My client does not support OAuth. What now?

Create an API key under API & Developers → API keys and send it in the `Authorization: ApiKey opk_…` header. A key can be limited to certain modules, read-only for example, and never reaches beyond its holder’s permissions.

### Do I need a specific permission to connect a client?

Yes: your role must include the API & Developers module. Without it, the connection is refused. Ask your workspace admin to add it.