# Step-by-step guides: the Ondes PRO MCP server and API in practice

> Four step-by-step guides to wire your website, build an integration, migrate your data or automate follow-ups with the Ondes PRO MCP server and REST API.

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

Each guide starts from a real goal — selling from a website that is already live, syncing a back office, leaving an old tool behind, handing off follow-ups — and walks through every step with **exact API requests**, snippets you can adapt and the part your **AI assistant connected over MCP** plays. Three are written for developers, the fourth for business owners.

## Which guide fits your project?

| Guide | Who it is for | What you end up with |
| --- | --- | --- |
| [Connect your website to the store](https://ondes.pro/en/integrations/mcp/guides/connect-your-website) | Developer of an existing site | Catalogue on your pages, cart and Stripe checkout handled by Ondes PRO, no rebuild needed |
| [Build an integration](https://ondes.pro/en/integrations/mcp/guides/build-an-integration) | Back-office developer, integrator | A service that reads and writes through the REST API, receives signed webhooks and never creates duplicates |
| [Migrate to Ondes PRO](https://ondes.pro/en/integrations/mcp/guides/migrate-to-ondes-pro) | Developer or technical lead | Catalogue, customers and billing records imported in verified batches, with AI doing the column mapping |
| [Automate with AI](https://ondes.pro/en/integrations/mcp/guides/automate-with-ai) | Business owner, manager | Reminders, reports and automations described in plain language, always reviewed before anything runs |

## Why MCP-oriented guides rather than a plain API reference?

The full API reference already lives in your workspace, generated from its real routes. What a developer usually lacks is the sequence: which objects to create first, where the idempotency key goes, how to test without charging anyone. Each guide answers those questions on one complete scenario.

The MCP server also changes how the work gets done. Your coding assistant no longer needs a documentation file pasted into the repository: it queries the workspace with `ondes_ressource` or `ondes_exemple` while it writes the code, and checks `ondes_impossible` before it invents a route. The guides show that pairing at work without making it mandatory — everything in them also runs with `curl`.

## Before you start: what you need

- An active Ondes PRO workspace (`https://<your-workspace>.ondes.pro`) on any plan: the API and the MCP server are included in all of them. No workspace yet? [Create one](https://ondes.pro/en/signup) or [try the demo](https://ondes.pro/en/demo).
- A role that opens **API & Developers**: that permission is required both to create a key and to connect an assistant.
- For a script or a server, a scoped **API key** (`billing:read`, `shop:write`…); for an assistant, an **OAuth** connection is enough.
- A **test mode** habit: resources with a twin are called under `/api/v1/test/…`, and a connected assistant writes there by default.

## Plug in your coding assistant before following a guide

Optional but worth it: with the connection below, your assistant reads your own workspace’s documentation as you go. Type your subdomain at the top of the page to personalise the command.

Where to set it up : One terminal command, then `/mcp` inside Claude Code to sign in.

**OAuth connection (recommended)** (Terminal)

```bash
claude mcp add --transport http ondes https://your-workspace.ondes.pro/mcp/
```

**API key connection** (Terminal)

```bash
claude mcp add --transport http ondes https://your-workspace.ondes.pro/mcp/ \
  --header "Authorization: ApiKey opk_…"
```

_Tested by our team. Vendor documentation : https://code.claude.com/docs/en/mcp_

> **A guide describes the API; your workspace describes your permissions** — The examples cite real resources — `shop/produits`, `billing/factures`, `developer/abonnements`. If your role does not open a module, its resources appear neither in the documentation served to your assistant nor in your API responses. Ask your workspace admin to adjust your role rather than hunting for a workaround route.

## Reference pages that go with these guides

- [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.
- [MCP vs REST API](https://ondes.pro/en/integrations/mcp/mcp-vs-rest-api) — What really sets them apart, when to pick which, and why at Ondes PRO they work together.
- [Stripe](https://ondes.pro/en/integrations/stripe) — Take store payments into your own Stripe account, company by company.

## Frequently asked questions

### Do I need to connect an AI assistant to follow these guides?

No. Every step relies on the Ondes PRO REST API and works with any HTTP client. The MCP server speeds things up by serving your workspace’s exact documentation to your coding assistant, but it is a companion, not a prerequisite.

### Do the guides work on the Essentiel plan?

Yes. The REST API, webhooks, test mode and MCP server are included in every Ondes PRO plan, Essentiel included. Only the user and storage limits differ, as listed on the [pricing](https://ondes.pro/en/pricing) page.

### Where is the full API reference?

In your workspace, under **API & Developers**: a sectioned guide, an explorer and an OpenAPI 3.1 schema, all generated from the real routes. Your assistant reaches the same material through the MCP server’s `ondes_guide` and `ondes_ressource` tools.

### Can I test without creating real orders or sending real emails?

Yes. Store orders, video meetings, email sends and invitations have a test twin under `/api/v1/test/`. For other resources, an assistant connected over MCP can validate a request body with `simuler: true` without saving anything.

### Do the guides cover multiple companies?

Where it matters, yes: one Ondes PRO workspace can hold a parent company and subsidiaries. A key or a connection only reaches its holder’s companies, and each guide points out where the company choice comes in.