Connect Ondes PRO to Visual Studio Code (GitHub Copilot)

Add the Ondes PRO MCP server to VS Code

You need VS Code with GitHub Copilot enabled. In an organisation, the Copilot admin may have turned MCP servers off: if nothing shows up, check that first.

1. 1

   Create the workspace file

   At the root of the open folder, create .vscode/mcp.json. You can also run “MCP: Add Server” from the Command Palette and pick an HTTP server: VS Code writes the file for you.

2. 2

   Declare the server under servers

   Careful: VS Code does not use the mcpServers key other editors use, but servers, with a type field set to http for a remote server.

   jsonCopy

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

3. 3

   Start the server

   Above the declaration, VS Code shows a “Start” action. On first start it asks you to confirm you trust this server, then to authorise the connection: a window from your Ondes PRO workspace opens, you sign in and approve the consent screen.

4. 4

   Switch chat to agent mode

   Open Copilot Chat and pick Agent mode. The tools button lists the ondes server’s tools: you can untick some of them — keep the documentation tools and drop the ones that write, for instance.

5. 5

   Ask something tied to your code

   For example: “Which events can I receive when a Kanban card is created?”. Copilot shows every tool call and waits for your approval before running it.

Copy-ready .vscode/mcp.json

The OAuth form holds no secret. The key form stores the key in plain text: prefer the inputs variant just below.

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

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

Hide the API key with inputs

If you use an API key — for a connection limited to one module, read-only for example — do not write it into the file. VS Code’s inputs array prompts for the value on first start, keeps it in the editor’s secure storage and substitutes it for ${input:ondes-cle}. The file can then be committed safely.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "ondes-cle",
      "description": "Ondes PRO API key (opk_…)",
      "password": true
    }
  ],
  "servers": {
    "ondes": {
      "type": "http",
      "url": "https://your-workspace.ondes.pro/mcp/",
      "headers": { "Authorization": "ApiKey ${input:ondes-cle}" }
    }
  }
}

Create the key under API & Developers → API keys: it is shown only once.

Workspace configuration or user configuration?

Example: subscribing Atelier Lumen’s production tool to new cards

Jules Perrin, a developer at Atelier Lumen, wants the workshop’s in-house tool to be notified as soon as a card lands on the Production board.

Good habits with Copilot and Ondes PRO

• Keep the six documentation tools on: they only read your workspace’s guide and inventory, nothing changes.
• Before a write, ask for a dry run: ondes_appeler with simuler: true validates the request body without saving anything.
• On resources with a test twin (orders, video meetings, email sends, invitations), writes go to test mode by default, and the response says so.
• Never commit a key: use inputs or OAuth, never a plain value in .vscode/mcp.json.
• If Copilot suggests an unknown endpoint, ask it to check with ondes_impossible: the tool lists what the API deliberately does not do.

Going further

• Build an integrationScoped keys, signed webhooks, idempotency and test mode for a back office that never creates duplicates.Read
• REST API v1Around 135 REST resources, scoped keys, an OpenAPI schema and signed webhooks.Read
• KanbanYour AI assistant creates, moves and comments on cards, and your teammates see it happen live.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
• ChatGPTChatGPT developer mode accepts your workspace as an MCP connector, over OAuth.Read
• WindsurfCascade plugs into your workspace through `mcp_config.json` and the `serverUrl` key.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