KSROlabs — Odoo AI, MCP Server & AnalyticsKSROlabs
Contact Us
Troubleshooting · MCP Server for Odoo

The AI sees fewer Odoo records than expected

Either a domain filter on the key's model access is restricting which records are visible, or the Odoo user the key acts as cannot see the rest under standard Odoo record rules. Check the filter first, then the user's groups.

What you are seeing

  • The assistant reports 12 open orders when Odoo shows 50
  • Records from one company, region or salesperson are missing
  • Totals from the assistant do not reconcile with an Odoo report
  • The same question returns different counts for two different keys

What causes it

A domain filter is restricting visible records, or the associated Odoo user does not have access via standard Odoo ACLs and record rules. Both are working as intended — the question is which one is in play, and whether the narrowing is the one you meant.

How to fix it

  1. Check the domain filter on the key's model access entry. Open MCP → Key Model Access, open the entry for that model, and read its domain filter. A filter left from a pilot — one company, one team, one date range — is the most common cause of a partial answer.
  2. Check the Odoo user's groups and record rules. The key acts as a specific Odoo user. If that user is restricted to their own records or to one company, the assistant inherits exactly that view. Compare by logging into Odoo as that user and running the same query.
  3. Decide which layer should do the narrowing. For a durable restriction, prefer the Odoo user's own rules — they apply everywhere, not only through MCP. Use the domain filter for restrictions specific to one AI client.
  4. Re-run the question and compare against the same Odoo view. Compare the assistant's answer with the list the same user sees in Odoo, not with what an administrator sees. Matching numbers mean the pipeline is correct and the difference was always a permission boundary.

How to confirm it is fixed

The assistant's count matches what its Odoo user sees in the interface. Any remaining gap is an Odoo permission question rather than an MCP one.

Related questions

Why does the AI see fewer Odoo records than I do?

Because it is not acting as you. The key is bound to an Odoo user, and the assistant inherits that user's record rules and company access — plus any domain filter set on the key's model access. If you are an administrator, you see more than the assistant by design.

Is a domain filter a security control or a convenience?

Both, but treat it as the second line. A domain filter narrows one key's view of one model, which is useful for scoping a single AI client. Odoo's record rules are the control that applies no matter how the data is reached, so anything that must never be visible belongs there.

If that was not it

The full setup reference lives in the MCP Server documentation, and How to connect Claude to Odoo walks through a clean install from the start. Free setup support is included with the MCP Server for Odoo — if none of the above matches what you are seeing, send us the audit log entry and we will read it with you.