# CRM MCP: an AI that keeps your sales follow-up current

> Ondes PRO’s CRM MCP server: your AI creates records, logs every conversation, moves deals through the pipeline and schedules follow-ups, then drafts the quote.

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

Ondes PRO’s **MCP server** connects your AI assistant to your workspace’s CRM. After a meeting or a call, it creates the contact’s record, logs the conversation, moves the pipeline stage forward and schedules the next follow-up — through the real `crm/fiches` and `crm/notes` resources. And since the CRM shares its database with invoicing, the quote can follow in the same conversation.

## Back from a trade show, the record fills itself in

_Example conversation · demo data (Atelier Lumen)_

> **You** : Met Claire Verdier from Maison Verdier at the show. She wants 20 bedside lamps for her guest rooms, tight budget. Create the record, log the conversation, mark her qualified and follow up on Tuesday.
>
> 🔧 `ondes_appeler` `GET crm/fiches?search=Verdier` — no existing record.
>
> 🔧 `ondes_appeler` `POST crm/fiches/creer-contact/` — record created, billing customer added in invoicing.
>
> 🔧 `ondes_appeler` `POST crm/fiches/64/noter/` with Tuesday’s follow-up — note saved, last contact updated.
>
> 🔧 `ondes_appeler` `POST crm/fiches/64/deplacer/` to the “Qualified” stage.
>
> **Assistant** : **Claire Verdier (Maison Verdier)** now has a record at the **Qualified** stage, with your note and a follow-up on Tuesday. She also exists as a customer in invoicing: shall I draft a quote for 20 bedside lamps for you to review before Tuesday?
>
> **You** : Yes, at the Atelier range price.
>
> 🔧 `ondes_appeler` `POST billing/devis` with `simuler: true`, then the real create — quote DEV-2026-0157 saved as a draft.
>
> **Assistant** : Quote DEV-2026-0157 is ready as a draft. Nothing has been sent to Maison Verdier.

## What your AI can read and do in the CRM

Ondes PRO’s CRM keeps one record per customer or prospect: company, job title, industry, segment, lead source, priority, account manager, pipeline stage and next follow-up date, plus the history of follow-up notes. Over MCP, the assistant reads all of it live and can find a record from a name, a company or an email address.

It acts through the CRM screen’s own moves: create a contact, add a note (which updates the last-contact date), move a record from one pipeline stage to the next — New, Qualified, Negotiation, Active customer, Inactive or Lost — and read the dashboard figures, including upcoming follow-ups.

## CRM resources available over MCP

| Resource or action | What the AI reads | What the AI can do |
| --- | --- | --- |
| `crm/fiches` | Customer records: company, segment, stage, owner, next follow-up | Update a record |
| `crm/fiches/creer-contact/` | — | Create a contact and, if you have invoicing, its billing customer |
| `crm/fiches/{id}/noter/` | — | Add a follow-up note, with an optional reminder |
| `crm/fiches/{id}/deplacer/` | — | Change the pipeline stage |
| `crm/fiches/tableau-de-bord/` | CRM figures and upcoming follow-ups | Read-only |
| `crm/notes` | Conversation history, author, date | Create or correct a note |

## Safeguards for a CRM in an AI’s hands

A CRM holds personal data. The server applies the same limits as the screen.

- **Customers only**: `crm/fiches` only serves customer and prospect records, never your colleagues’, which have no place in a sales pipeline.
- **No record deletion**: the resource can be read, created and updated, but not deleted through the API.
- **Cross-module permissions**: the billing customer is only created alongside the contact if your role also opens invoicing.
- **One record per person**: the assistant looks for an existing record before creating one, and contact creation reports when the person already existed.
- **Real writes are flagged**: the CRM has no test twin, so every write is reported as real in the response.

## Typical requests and what happens

| You ask | What the assistant does |
| --- | --- |
| “Who should I follow up with this week?” | Reads `crm/fiches/tableau-de-bord/` and lists scheduled follow-ups with their owner. |
| “Log my call with Brasserie La Canopée: they’re unsure about lead times.” | Adds a note through `noter/` and suggests a follow-up date. |
| “Move Studio Nord to negotiation and hand the account to Hugo.” | Calls `deplacer/`, then updates the account manager. |
| “Which trade-show leads are still at the New stage?” | Filters records by lead source and stage, then summarises the list. |
| “Sum up everything we know about Le Comptoir des Marées.” | Reads the record and its notes, and can cross-check the same customer’s quotes and invoices. |

## A CRM wired into the rest of the business

An MCP server tied to a standalone CRM knows where a prospect stands, not what they bought or what they owe. In Ondes PRO, a customer record shares its database with [invoicing](https://ondes.pro/en/integrations/mcp/modules/invoicing) and [the online store](https://ondes.pro/en/integrations/mcp/modules/online-store): the assistant can match an open negotiation with a pending quote, or spot an unpaid invoice before offering a discount.

Sales follow-up also carries into day-to-day organisation: a presentation meeting in [the calendar](https://ondes.pro/en/integrations/mcp/modules/calendar), a demo through [video conferencing](https://ondes.pro/en/integrations/mcp/modules/video-conferencing), a prep task in [Kanban](https://ondes.pro/en/integrations/mcp/modules/kanban). You phrase the request once; the assistant moves between modules.

> **Your customers’ data stays with you** — Your Ondes PRO workspace is a dedicated instance hosted in France. The MCP server sends nothing on its own: the assistant you connect reads what it needs to answer. To learn more, see [MCP server security](https://ondes.pro/en/integrations/mcp/security) and [our security page](https://ondes.pro/en/security).

## Keep exploring

- [Web agencies and IT services](https://ondes.pro/en/integrations/mcp/industries/web-agencies) — One MCP server per client, documentation that is always accurate, and a test mode to ship without breakage.
- [MCP vs Zapier, Make, n8n](https://ondes.pro/en/integrations/mcp/mcp-vs-zapier-make-n8n) — A dated, sourced comparison of two different takes on connected AI, and why they complement each other.
- [Modules available over MCP](https://ondes.pro/en/integrations/mcp/modules) — Eleven business modules behind one MCP server: what the assistant can read and do in each.

## Frequently asked questions

### Can an MCP server connect to a CRM?

Yes. Ondes PRO builds an MCP server into every workspace: a compatible assistant such as Claude can read and update CRM customer records and follow-up notes, with the permissions of the person who connects it.

### Can the AI delete customer records?

No. The `crm/fiches` resource lets you read, create and update a record, but not delete it through the API.

### Which pipeline stages does the assistant know?

Those of the Ondes PRO CRM: New, Qualified, Negotiation, Active customer, Inactive and Lost. The `deplacer/` action moves a record from one to another.

### Can it schedule a follow-up?

Yes. When adding a note through `noter/`, the assistant can set the next follow-up date; upcoming follow-ups then appear on the CRM dashboard.

### Do the CRM and invoicing share the same customers?

Yes. Creating a contact with `creer-contact/` also creates its billing customer when your role opens invoicing, so you can move straight on to a quote without retyping anything.

### Is my customer data used to train an AI?

Ondes PRO sends no data on its own. What the assistant does with the conversation depends on the vendor you chose and its privacy settings.