Connect a code editor

Connect Ondes PRO to Zed

Zed calls MCP servers context servers and declares them under the context_servers key of its settings. For Ondes PRO an address is enough: with no authentication header, Zed starts the OAuth sign-in with your workspace by itself. The Agent Panel can then read your resources’ documentation and act on your data, at your pace.

Standard MCP compatibleUpdated on 21 October 2026

Your Ondes PRO workspace

https://.ondes.pro/mcp/

Type your workspace name: the configurations on this page adapt. It is remembered in this browser only.

Declare Ondes PRO as a context server in Zed

The shortest configuration of any editor: three meaningful lines, no key.

Open Zed’s settings
From the command palette, open the settings file (settings.json). An entry added here applies to all your projects.
2
Add the context_servers entry
Paste the block below at the top level of the file, next to your other settings. Replace the subdomain, or type it at the top of the page.
json
```
{
  "context_servers": {
    "ondes": { "url": "https://your-workspace.ondes.pro/mcp/" }
  }
}
```
Let Zed start the authorisation
Because the entry carries no Authorization header, Zed detects that the server expects OAuth and opens a window from your Ondes PRO workspace. Sign in and approve the consent screen.
Check the server status
In the Agent Panel settings, the ondes server appears with a status indicator. Once active, its eight tools are offered to the agent.
Use it in the Agent Panel
Open the Agent Panel and ask, for example, “Which columns does the Website board have?”. Zed asks for confirmation before running a tool, unless you chose to always allow.

Copy-ready context_servers configuration

With an Authorization header, Zed does not start OAuth, so the second form is only for when you want a restricted API key. The settings file is personal, so the key does not end up in a repository.

ZedStandard MCP compatible

Where to set it up : The context_servers key of Zed’s settings file.

OAuth connection (recommended)

No key to copy: a window from your Ondes PRO workspace opens to authorise the connection.

settings.json

{
  "context_servers": {
    "ondes": {
      "url": "https://your-workspace.ondes.pro/mcp/"
    }
  }
}

API key connection

Create a key in API & Developers → API keys, then replace opk_… with its value.

settings.json

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

This client follows the open MCP protocol. Our team has not yet validated the connection end to end: the steps below follow its vendor’s documentation.

Vendor documentation : zed.dev

Choosing which Ondes PRO tools Zed’s agent can use

Zed groups the agent’s tools into profiles. You can create one that only enables the Ondes PRO server’s six documentation tools — ondes_etat, ondes_guide, ondes_chercher, ondes_ressource, ondes_impossible, ondes_exemple — to code against your workspace’s exact documentation with no way to write.

For tasks where the agent must act, a second profile adds ondes_appeler and ondes_assistant. Even then, several safety nets remain: Zed’s confirmation before each tool, your Ondes PRO permissions bounding everything, a dry run available on any resource, and test mode by default on resources that have a test twin.

The eight tools Zed sees

Always the same ones, however many modules your workspace has: the depth sits behind them, not in their list.

ondes_etatRead
Connection status
Who is connected, which modules are reachable and which permissions the connection carries. The assistant calls it once to learn its scope.
ondes_guideRead
API guide
The API guide, section by section: a summarised table of contents first, then only the sections that matter (pagination, idempotency, payments…).
ondes_chercherRead
Search
Searches a business term (“quote”, “stock”, “webhook”) across both the resource inventory and the guide.
ondes_ressourceRead
Resource sheet
Everything needed to call one resource correctly: URL, verbs, typed and required fields, filters, ordering, actions, required permission, test twin.
ondes_impossibleRead
What the API does not do
The list of what deliberately does not exist. The assistant checks it before inventing a URL: this is what keeps it from hallucinating.
ondes_exempleRead
Complete recipes
Whole scenarios already verified against the real API: create, read without N+1 calls, invoice, subscribe to events.
ondes_appelerWrite
Call the API
Runs a real call with the user's identity. Writes go to test mode by default, and a dry run validates a request without writing anything.
ondes_assistantWrite
Ask the Ondes PRO assistant
Asks a business question to the built-in assistant, which aggregates several modules. Its writes come as a plan, executed only after approval.

Example: turning TODOs into Kanban cards

Léa is wrapping up Atelier Lumen’s website redesign. TODOs are scattered through the code; she wants them on the team’s “Website” board.

Zed (Agent Panel) · Example conversation · demo data (Atelier Lumen)

You : Collect the TODOs in src/ and create one card per TODO in the “To do” column of the Website board, with the file in the description.
MCP tool : ondes_ressource kanban/cartes sheet: column and title required, no test twin — a creation is real.
MCP tool : ondes_appeler GET kanban/colonnes filtered on the Website board — the “To do” column is found.
MCP tool : ondes_appeler POST kanban/cartes with simuler: true on the first card — valid body, nothing written.
Assistant : I found 7 TODOs, including “compress the Suspension Pétrole photos” and “translate the Shipping page”. The dry run passes. Since kanban/cartes has no test mode, creation will be real: shall I create the 7 cards?
You : Yes.
MCP tool : ondes_appeler 7 × POST kanban/cartes — “real write” stated in each response, cards created.
Assistant : Done. The cards appeared live for teammates who have the board open; each one shows the file and line of its TODO.

Going further

Frequently asked questions

How do I add a remote MCP server to Zed?

Add an entry under context_servers in settings.json, with the server address in url. For Ondes PRO: "ondes": { "url": "https://<your-workspace>.ondes.pro/mcp/" }. Zed then starts the OAuth sign-in.

Do I need an API key to connect Zed to Ondes PRO?

No. Without an authentication header, Zed runs the OAuth sign-in with your workspace on its own. An API key is only useful if you want a connection limited to certain modules or to read-only access.

Can I restrict Zed to reading the documentation?

Yes, with an agent profile that only enables the six documentation tools. The agent keeps access to your workspace’s guide and resource sheets, without ondes_appeler or ondes_assistant.

Does a card created from Zed show up for the team right away?

Yes: Ondes PRO Kanban boards are real-time whatever the source of the write. A card created by the agent appears live for teammates who have the board open.

Has the Ondes PRO team tested Zed?

No, Zed is listed as “standard MCP compatible”: its context_servers entry follows the protocol our server implements, OAuth discovery included, so the connection should work. Only Claude has been verified end to end by our team; if a Zed setting is renamed, Zed’s documentation is the reference.

Plug your AI into your business

The MCP server is included in every plan, with no add-on or extra fee.

Create my workspace See pricing