Skip to Content

Cledoo: Odoo MCP Server - Free - Claude, GPT, Copilot

by
Odoo
v 19.0 Third Party 25
Download for v 19.0 Deploy on Odoo.sh Live Preview
Versions 18.0 19.0
You bought this module and need support? Click here!
Versions 18.0 19.0
Cledoo
LGPL-3 ODOO 18 ODOO 19 MCP

FREE & OPEN SOURCE · NATIVE ODOO MODULE · NO EXTERNAL SERVER

Claude talks
to your Odoo.

Install the module, flip one switch, connect Claude — or ChatGPT, Copilot, Le Chat, any MCP client. Every call runs as the connected user, under their existing Odoo rights — nothing more.

17 MCP tools Set up in 5 minutes

Unpaid invoices, Paris branch?

search_records → 3 results ✓

3 overdue invoices — €24,980 total, oldest INV/2026/0142 at 18 days.

WORKS WITH ANY MCP CLIENT

Claude.ai & Claude Desktop ChatGPT GitHub Copilot Mistral Le Chat Cursor + any MCP client

SECURE BY DESIGN

Your Odoo permissions stay the only rule.
No separate rights system to misconfigure.

ACLs & record rules

Every call runs as the connected user — exactly what they'd see in the interface, field rights included.

No external server

The module runs inside your instance. Nothing leaves your server, no SaaS relay, no middleman.

Built-in OAuth 2.1

Odoo consent screen, revoke any connected agent in one click from Settings. No API key to pass around.

Why teams install it

One-click connection from AI chat apps

Built-in OAuth 2.1 with a branded consent screen: paste your MCP URL into claude.ai, ChatGPT or Le Chat, log into Odoo, approve. Plain Odoo API keys work side by side for header-capable clients.

Token-efficient by design

A curated, admin-editable model catalog — not a 500-model dump — compact field metadata, no inline binary blobs, pagination probes and a 100 kB response guard. The AI spends its context on answers, not noise.

Your permissions, enforced

Every call runs as a real Odoo user under their ACLs and record rules — give the AI a dedicated user to control exactly what it can touch.

MCP chatter badge

Messages written through MCP get a small "MCP" badge with the AI client's name, so humans always know who wrote what.

Chatter message tagged with an MCP badge - written via MCP by Claude

Built for operations

A /mcp/health endpoint that self-diagnoses common deployment issues, per-connection rate limiting, per-agent activity counters. Multi-company aware. Tested on Odoo 18 and 19.

Zero dependencies

Stdlib-only Python, no extra process to host, nothing new to deploy or monitor.

THREE STEPS, AND YOU'RE SET

Connected in 5 minutes.

STEP 1

Install the module

From the Odoo Apps Store, on your on-premise or Odoo.sh instance — use the branch matching your series, 18.0 or 19.0.

STEP 2

Enable MCP

One switch in Settings > General Settings > MCP Server. Your instance's /mcp endpoint is ready.

STEP 3

Connect Claude

Paste the URL in claude.ai, log into Odoo, approve. Any other client connects with an Odoo API key as a bearer token.

STEP 1 IN DETAIL — INSTALLING THE ZIP

  1. Unzip the archive — you get a cledoo_mcp/ folder.
  2. Copy it into an addons directory of your server (any path listed in addons_path in odoo.conf).
  3. Restart the Odoo service.
  4. Enable developer mode, then Apps > Update Apps List.
  5. Search for Cledoo MCP and click Install.

On Odoo.sh, commit the cledoo_mcp/ folder to your linked GitHub repository instead — the next build installs it.

Enable the MCP server in Settings

Step 2 — one toggle, one endpoint URL, everything managed from Settings.

Add your Odoo as a custom connector in claude.ai

Step 3 — paste your /mcp URL as a connector in claude.ai.

Odoo OAuth consent screen - authorize Claude

Log into Odoo, approve — the AI acts with your Odoo permissions, never more.

Claude answering questions live on Odoo data

Done — Claude, live on your Odoo data.

A CURATED CATALOG, NOT A 500-MODEL DUMP

17 MCP tools — everything an agent needs to answer questions and act on your data.

DISCOVER

whoami list_models list_modules get_model_fields describe_access

READ & ANALYZE

search_records get_record count_records aggregate_records export_records read_resource

ACT

create_record update_record delete_record post_message get_messages print_report

Security model

This module deliberately adds no policy engine of its own:

  • Every caller is authenticated as a real Odoo user (API key or OAuth token).
  • Every ORM call runs under that user's ACLs, record rules and field rights.
  • Write tools (create_record, update_record, delete_record, post_message) run plain create/write/unlink as that user — the backstop is that user's Odoo rights. Give the AI a dedicated user with tight ACLs.

OPTIONAL ADD-ON

Need to govern what the AI can do?

Cledoo MCP gives the AI access, bounded by each user's Odoo rights. A separate module, Cledoo MCP Pro, adds governance over the AI itself: a global read-only kill-switch and per-connection scopes, a full, exportable audit trail, data privacy masking even in exports, per-user allow/deny policies with a dry-run simulator, human-confirmed writes, and an outbound-comms guard. Available on the Odoo Apps Store.

Data privacy: no data collected by default. One opt-in, off-by-default anonymous usage ping (no customer data) — details in the Privacy Policy. Not installable on Odoo Online (SaaS): custom modules require Odoo.sh or an on-premise deployment.

Documentation

Configuration (Settings > MCP Server)

  • Enable MCP Server — master switch. While off, /mcp returns 404.
  • Featured models — the curated model catalog the AI sees first; edit it to match your business.
  • Rate limit — per-connection request budget on /mcp (requests per minute, 0 disables).
  • Max inline size — ceiling (MB) for tools that inline a whole file or export into the response.
  • Tag MCP chatter messages — show the "MCP" badge on messages written by AI clients.
  • Connected AI clients — review and revoke OAuth-connected agents, view activity and sessions.
  • Anonymous usage statistics — opt-in, off by default.

Authentication

  • OAuth 2.1 (recommended for claude.ai) — paste https://your-odoo.example.com/mcp as a custom connector, log into Odoo, approve on the consent screen. Revoke anytime from Settings.
  • Odoo API key — generate one under Preferences > Account Security > New API Key, send it as Authorization: Bearer <key>. Works with any header-capable MCP client.

Operations

  • Health check — open /mcp/health to self-diagnose the most common deployment issues (proxy, auth, database routing).
  • Multi-company — calls follow the connected user's allowed companies.
  • Requirements — Odoo 18 or 19, On-Premise or Odoo.sh. No extra Python dependency. Not installable on Odoo Online (SaaS).

Quick install

  1. Download the module (or buy it here on the Apps Store) and unzip: you get a cledoo_mcp/ folder.
  2. Copy it into an addons directory of your server (a path listed in addons_path in odoo.conf). On Odoo.sh: commit the folder to your linked GitHub repository.
  3. Restart Odoo, enable developer mode, then Apps > Update Apps List, search "Cledoo" and click Install.
  4. Go to Settings > General Settings > MCP Server, tick Enable MCP Server, save. Your endpoint URL is displayed right there.

Add the connector in Claude (OAuth)

  1. In claude.ai or Claude Desktop: Settings > Connectors > Add custom connector.
  2. Name it (e.g. "Odoo"), paste your endpoint https://your-odoo.example.com/mcp, leave the OAuth fields empty, click Add.
  3. Click Connect: you are redirected to your Odoo login page.
  4. Log into Odoo. The consent screen appears: "Claude is requesting access to your Odoo account", listing exactly what it can do. Click Allow access.
  5. Back in Claude, the Odoo tools are live — ask "What can you see in my Odoo?" to test.

To revoke later: Settings > MCP Server > Manage connections in Odoo — or remove the connector in Claude. See the screenshots above for both screens.

FAQ

Which AI clients work? Claude.ai and Claude Desktop (OAuth, one click), and any MCP client that speaks streamable HTTP with bearer auth: ChatGPT, GitHub Copilot, Mistral Le Chat, Cursor, custom agents.

Can the AI see more than the user? No. Every call runs under the connected user's ACLs, record rules and field rights — exactly the UI perimeter.

How do I restrict what the AI can do? Connect it as a dedicated Odoo user with tight ACLs. For governance of the AI itself (read-only kill-switch, scopes, audit, masking, confirmed writes), see the separate Cledoo MCP Pro module on the Odoo Apps Store.

Does anything leave my server? No. The module runs inside your instance; there is no relay. Telemetry is opt-in and off by default.

Support

Questions, issues or feature requests: support@cledoo.com. We answer fast, in English or French.

License

LGPL-3 — free and open source. The full license text ships with the module (LICENSE file). You can read, audit and extend the code.

Changelog

1.7.0 (2026-07-20) — first public release on the Odoo Apps Store.

  • 17 MCP tools (discover, read & analyze, act) running under native Odoo ACLs.
  • Built-in OAuth 2.1 authorization server with consent screen, plus Odoo API-key auth.
  • Curated featured-models catalog, per-connection rate limiting, response-size guards.
  • MCP chatter badge, connected-clients management, /mcp/health self-diagnosis.
  • Opt-in anonymous usage statistics (off by default). English and French translations.
  • Odoo 18 and 19 support.
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 2325
Technical Name cledoo_mcp
LicenseLGPL-3
Websitehttps://cledoo.com

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.