# Connect Ondes PRO to Cline

> Add the Ondes PRO MCP server to Cline: cline_mcp_settings.json with type streamableHttp, OAuth through cline mcp authorize, and tool-by-tool approval.

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

Cline is a coding agent that lives in your editor and asks before every action. It connects to **remote MCP servers** with an explicit transport: for Ondes PRO, `type: streamableHttp`. Once connected, it reads your workspace’s real documentation, prepares its calls and lets you decide, tool by tool, what it may do without asking.

## Add Ondes PRO to Cline’s MCP servers

The one thing not to miss: Cline distinguishes two remote transports, and the Ondes PRO server speaks “Streamable HTTP”. Declared with the other type, it will not answer.

1. **Open the MCP Servers panel** — In Cline, click the MCP servers icon. You can add a remote server from its dedicated tab, or click **Configure** to edit `cline_mcp_settings.json` directly.
2. **Declare the server as streamableHttp** — In the file, add an `ondes` entry under `mcpServers`, with the type and your workspace address.

```json
{
  "mcpServers": {
    "ondes": {
      "type": "streamableHttp",
      "url": "https://your-workspace.ondes.pro/mcp/"
    }
  }
}
```
3. **Authorise the connection** — If Cline does not offer to sign you in on its own, run `cline mcp authorize` from the Cline CLI. A window from your Ondes PRO workspace opens: sign in and approve the consent screen.
4. **Check the tools** — The `ondes` server turns green in the panel and its eight tools are listed. That is where you set auto-approval for each one.
5. **Hand Cline a task** — For example: “Explain how storage buckets work in my workspace”. Cline shows you every tool call before running it.

## Copy-ready cline_mcp_settings.json

The OAuth form holds no secret. The API key form is for a deliberately restricted connection.

Where to set it up : Cline’s **MCP Servers** panel, then **Configure** (`cline_mcp_settings.json`).

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

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

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

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

_Standard MCP compatible. Vendor documentation : https://docs.cline.bot/mcp/connecting-to-a-remote-server_

## Which Ondes PRO tools should Cline auto-approve?

Cline lets you tick, tool by tool, the ones it may use without asking (the setting is saved in the entry’s `autoApprove` list). The six documentation tools are good candidates: `ondes_etat`, `ondes_guide`, `ondes_chercher`, `ondes_ressource`, `ondes_impossible` and `ondes_exemple` only read your workspace’s guide and inventory. Approving them saves a confirmation every time Cline checks a field name.

Keep `ondes_appeler` and `ondes_assistant` behind confirmation, though. The first runs real API calls with your identity; the second queries the built-in assistant, which can propose changes. Even once confirmed, those calls stay fenced on the Ondes PRO side: dry runs, test mode by default on resources with a test twin, and the mode always stated in the response.

## Example: moving product photos to the CDN

_Example conversation · demo data (Atelier Lumen)_

> **You** : Create a public “catalogue” bucket in Ondes PRO, then write a script that uploads the `photos/` folder without duplicates if we rerun it.
>
> 🔧 `ondes_ressource` `stockage/buckets` sheet: `nom` and `visibilite`; `stockage/objets` sheet: multipart upload or JSON `contenu_base64`.
>
> 🔧 `ondes_guide` Idempotency section: an `Idempotency-Key` is refused on a multipart body, accepted on the `contenu_base64` form.
>
> 🔧 `ondes_appeler` `POST stockage/buckets` with `simuler: true` — valid body. Then, after your approval, a real creation is stated: public “catalogue” bucket.
>
> **Assistant** : The bucket exists. The `migrate_photos.py` script sends each image as `contenu_base64` with an idempotency key derived from its path: rerun after a dropout, it creates no duplicates. Identical files are deduplicated by their hash, and each object gets a long-cached `?v=` URL. There are 148 photos, including the Lampe Trépied and the showroom armchair. Shall I run a trial on the first five?

## Cline: a careful agent in front of a business API

What makes Cline a good fit for Ondes PRO is that both share the same philosophy. Cline does nothing without showing you the action; the Ondes PRO server never documents a resource to the agent that would answer “access denied”, returns business refusals as readable results rather than errors, and states in every response whether a write was real, in test or simulated.

The upshot: Cline corrects itself when a field is missing instead of looping on an obscure error, and you always know what actually changed in your workspace. To see why this differs from plain API access, read [MCP vs REST API](https://ondes.pro/en/integrations/mcp/mcp-vs-rest-api).

> **Revoke Cline in one click** — Every Cline OAuth connection appears in the **MCP** tab of **API & Developers**, named after the machine. “Revoke” cuts it off at once, without waiting for the one-hour token to expire. If you use Cline on two computers, those are two separate connections, revocable independently.

## Going further

- [Object storage & CDN](https://ondes.pro/en/integrations/mcp/modules/object-storage-cdn) — File buckets served by a CDN, which your coding assistant creates and fills for your websites.
- [Migrate to Ondes PRO](https://ondes.pro/en/integrations/mcp/guides/migrate-to-ondes-pro) — Bring over catalogue, customers and billing records in verified batches, with AI doing the column mapping.
- [REST API v1](https://ondes.pro/en/integrations/rest-api) — Around 135 REST resources, scoped keys, an OpenAPI schema and signed webhooks.
- [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

### Which transport type should I pick in Cline for Ondes PRO?

`streamableHttp`. The Ondes PRO MCP server uses the protocol’s “Streamable HTTP” transport. Declared with another type, the connection fails.

### How do I authenticate Cline with Ondes PRO?

With OAuth: declare the address `https://<your-workspace>.ondes.pro/mcp/` without a header, then authorise the connection in your workspace window — running `cline mcp authorize` if needed. An API key in `headers` remains possible for a restricted connection.

### Can Cline use the Ondes PRO tools without confirmation?

You can auto-approve the six documentation tools, which only read the guide and inventory. We recommend keeping `ondes_appeler` and `ondes_assistant` behind confirmation, since they act on your data.

### Can Cline upload files to Ondes PRO?

It can create storage buckets and objects through the API, with your permissions. For many files, the most efficient approach is to have it write a script that calls the API directly, based on the documentation it read over MCP.

### Has the Ondes PRO team tested Cline?

No. With the `streamableHttp` type, Cline uses our server’s standard transport, so the connection should work. Only Claude has been verified end to end by our team; Cline moves fast, and its remote-server documentation is the reference.