04 ·Agnidoot MCP
Give Claude, ChatGPT and your own agents a governed route into Odoo. Eight of seventeen tools are on by default — every one of them read-only. Everything that changes anything is off until you turn it on.
Tools available
On by default
all read-only
Risk tiers on
every action
Correlation ID
across every call
The idea
This is the chokepoint the rest of the platform is built on. Because every AI call to Odoo passes through it, the audit trail is complete by construction rather than best-effort — and a policy you set once applies to every AI your company uses.
Search, get, aggregate, schema, resolve, diagnostics, export and trace — on from day one. Writes, business actions, deletes, attachments and introspection are each behind their own gate, off until switched on.
Risk tiers 0–4 on every action. A consequential call prompts a human — and if no human can be asked, it fails closed rather than proceeding quietly.
Every call from every AI lands in one auditable timeline under a single correlation ID — refusals included.
Controls
The honest comparison
We're not going to pretend otherwise. Native MCP solves connectivity, and connectivity is becoming a feature rather than a product. The next question is how much governance you need around it.
| The question | Native MCP | Agnidoot MCP |
|---|---|---|
| Connect an AI client to Odoo | ✓ | ✓ |
| Read-only defaults with per-capability gates | — | ✓ |
| Risk tiers on every action | — | ✓ |
| Human confirmation, failing closed | — | ✓ |
| Per-client scoped keys and quotas | — | ✓ |
| One correlation ID across document, chat and write | — | ✓ |
| A path into organisation-wide AI control | — | ✓ |
Use native MCP if you want one developer connecting one AI client to one Odoo. Use this if several people and several AI tools will touch the ERP, and somebody will eventually have to prove what they did.
Running it
The fastest start. Your team points their AI clients at it and works. No infrastructure to manage.
For regulated work: run it inside your own network, even air-gapped, with a local model. Nothing leaves your walls.
It governs the AI paths this platform owns. A person editing a record by hand inside Odoo is governed by Odoo's own permissions, exactly as before. And no penetration test has been performed — we'll hand your security tester the code and walk them through the enforcement points that exist today.
Every plan includes
No obligation, no card, no lock-in. And what comes with your plan isn't a discount — it's what it takes to make an ERP actually land.
Not months. Your implementation is underway in your first week.
A full year included with every plan — not a paid add-on.
We come to you and train your team in the room, on your data.
A hundred hours of our engineering, built into every plan.
◆ No card to start · ◆ No obligation · ◆ Cancel any time in the three months · ◆ Your data stays yours
Questions
Start read-only, widen deliberately, and watch every call land in one trace.
Thirty minutes, your paperwork, your questions. We will show you what it does — and, just as importantly, what it refuses to do.
