Skip to Content

Connecting an AI assistant to Odoo through MCP

An existing open source connector, a manual written for the assistant, a small Stripe script made redundant: what is mine, and what is not.
November 15, 2026 by
Connecting an AI assistant to Odoo through MCP
Federico Solutions, Myrko Federico

Connecting an AI assistant to Odoo through the MCP protocol

Field: Odoo ERP, AI assistants, integration

Period: since April 2026, in daily use

Client: internal project, my own companies (Lab 77, R&D)

Asking your AI assistant which invoices are still open, or to publish a page in three languages, and having it do so directly in the ERP: that is what the MCP protocol makes possible. I have been working this way with Odoo since April 2026. Here is what, in this setup, is a third-party tool, what I wrote myself, and what I learned from it.

Context

Odoo is the ERP of my companies: sales, accounting, websites, calendar. I wanted my AI assistant to be able to read and write in Odoo, now installed on my own server, rather than copying figures from one window to another. The MCP protocol (Model Context Protocol), which has become the standard plug between AI assistants and software, was the natural route.

Problem

  • The connector is not enough: giving the assistant the means to search and write in Odoo does not teach it how Odoo works, or its pitfalls.
  • Costly pitfalls: a translated field modified carelessly, for example, can lose its translations. The assistant must know this before writing, not after.
  • Limited context: explaining everything to the assistant at once saturates its working memory and is expensive on every request.
  • One subscription too many: bringing Stripe transactions into the accounts then went through a paid aggregation service, billed per currency and per month.

Solution

1. Use an existing connector, not write one

The MCP server I use is not mine: it is mcp-server-odoo, an open source project published under the MPL-2.0 licence. It gives the assistant tools to search, read, create, modify and delete records, compute totals and post a message in a document's thread. I kept it: it was already working.

2. Write the manual the assistant does not have

My contribution is the knowledge layer: a manual of about a thousand lines, split into nine chapters that the assistant loads only when it needs them. It covers the basics (field types, search filters, totals), then the online shop, web pages, calendar and appointments, e-learning, the blog and link tracking. It brings together Odoo's official documentation, generic knowledge taken from the odoo-toolbox kit, whose knowledge sheets are released into the public domain (CC0), and above all the pitfalls I ran into for real.

3. A small script for Stripe, until something better came along

In May 2026, on Odoo Online, I replaced the paid aggregation service with a scheduled script. Every month, it reads the Stripe transactions with read-only access, records them in Odoo as an ordinary bank statement, net amounts with the fees noted on each line, and gives each line a unique reference so that a second run creates no duplicates. It also archives each statement in the standard banking format. Since my migration to Odoo Community, an open source module from the OCA (Odoo Community Association) does the same thing inside Odoo: I switched to the standard module.

Result

The assistant works in Odoo every day: this is how it helps me keep my accounts and manage the content of my websites. The rules that frame what it is allowed to do are described in an article on MCP security: I will not repeat them here.

I also wrote an MCP server for SiYuan, the note-taking tool I use. It too started from an existing open source project, and adds reading and writing of SiYuan's databases. It is published free of charge on GitHub, under the MIT licence; I present it in a dedicated article.

What I take away

  • The connector is a pipe; the value is in the knowledge. The connector gives the assistant the means to act; the manual is what spares it the errors already known.
  • Load the knowledge chapter by chapter. A manual that is split up and loaded on demand costs less and stays readable, for the assistant as for me.
  • Do not reinvent what exists. The connector, the generic knowledge, then the Stripe module: each time, an open source project already did the job. I only wrote what was missing.
  • A home-made script is a bridge. It did its job and saved a subscription. But as soon as a standard module, maintained by a community, did the same thing, I preferred it.
  • The agent has the rights of its account. What the assistant can do in Odoo is what the account it connects with is allowed to do. That is where security is settled.

Going further

Do you want an AI assistant to work in your ERP, with clear rules on what it may read and write? I design these integrations and the manual that makes them reliable. See sovereign AI, or book a 20-minute discovery call.

Sources

Tags: Odoo, MCP, AI assistant, ERP, integration, Stripe, OCA, SiYuan, open source software

Home Assistant: from Raspberry Pi to Docker
A migration of under an hour, a revised verdict, a six-month fault finally understood, and monitoring that was creating the fault.