Cledoo

Security

Odoo's own security. Nothing more, nothing less.

The AI sees and does exactly what the connected Odoo user can — no more, no less. Cledoo MCP authenticates every caller as a real Odoo user and runs each call under their ACLs and record rules; it adds no separate rules engine, and no data ever leaves your instance. Advanced governance — masking, audit, confirmed writes — is what Cledoo MCP Pro adds.

  • No third-party server

    The module runs inside your Odoo instance. No request, no data ever transits through a Cledoo server.

  • Native Odoo permissions

    Every MCP call runs with the connected user's ACLs and record rules — exactly what they can see and do in the Odoo UI.

  • Writes unconstrained beyond ACLs (base module)

    On Cledoo MCP, create/update/delete follow only the user's Odoo rights — like any direct ORM access.

  • Advanced governance with Pro

    A global read-only kill-switch, data privacy masking, role-based policies, human-confirmed writes and an exportable audit log.

  • Auditable code

    The module and how it works are documented and reviewable — no black box between Claude and your Odoo.

Getting started

Three steps, and you're live.

01

Install the module

From the Odoo Apps Store (Cledoo MCP, free) or by uploading the module file to your On-Premise / Odoo.sh instance.

02

Activate and connect

A toggle in Settings > MCP. Generate an Odoo API key, or use the built-in OAuth 2.1 flow to connect claude.ai in one click.

03

Your teams use their AI

Claude, or any MCP client, as usual. Each person acts with their own Odoo account and rights.