Every Odoo MCP Server Compared: Which One Actually Works for You? (2026)
AI assistants like Claude and ChatGPT can now read and write your Odoo data directly. Ask "show me all unpaid invoices over 5,000 EUR from Q4" and get an instant answer — no exports, no filters, no domain syntax. This works through MCP (Model Context Protocol), an open standard that connects AI tools to external systems.
There are 9+ projects that offer this for Odoo. But which one should you actually use? That depends on one key question:
Where do you want to use it?
If you only need it on your laptop with Claude Desktop or Claude Code installed, most solutions work fine. But if you want to check stock from your phone during a warehouse visit, look up a customer while you're in a meeting, or create a lead from the train — you need a solution that works everywhere.
Here's the thing: most Odoo MCP servers run as a local process on your computer (called STDIO transport). That means they only work on the machine where you installed them. To use Odoo + AI from your phone, tablet, or any browser, you need a server that runs remotely (Streamable HTTP transport). That narrows the field significantly.
The options
Works everywhere (phone, desktop app, browser, Claude Code)
pantalytics/odoo-mcp-pro — The only hosted option. Sign up, enter your Odoo URL + API key, connect Claude (or ChatGPT), done. No install, no Docker, no command line. Works on:
- Claude mobile app (iOS/Android) — query Odoo from anywhere
- Claude.ai in your browser — any device, any OS
- Claude Desktop app — Mac and Windows
- Claude Code — for developers
- ChatGPT and other MCP-compatible tools
Supports Odoo 14-19+, auto-detects whether to use JSON/2 or XML-RPC. Your Odoo permissions apply — users can only see what their role allows. API keys encrypted at rest. Free during beta: pantalytics.com/en/apps/odoo-mcp-server
Also available as self-hosted Docker deployment if you want full control over your infrastructure.
Works on your laptop only (local install required)
ivnvxd/mcp-server-odoo — The most mature local option. 6 tools with smart field selection. API key auth. Install via uvx mcp-server-odoo. Optional paid Odoo module (EUR 99) for granular access controls. Odoo 14-18, XML-RPC only.
tuanle96/mcp-odoo — The simplest to get started. 3 tools, password auth. Install via pip install odoo-mcp. Good for a quick test to see if MCP + Odoo is useful for you.
hachecito/odoo-mcp-improved — Pre-built tools for sales, purchases, inventory, and accounting workflows. Good if you want domain-specific operations out of the box.
marcfargas/odoo-toolbox — TypeScript/Node.js. The only non-Python option. Full CLI + SDK with a skill-module architecture. Very actively maintained and CI-tested against real Odoo instances.
rachmataditiya/odoo-rust-mcp — Written in Rust. Supports JSON/2 + JSON-RPC, multiple transports including HTTP and WebSocket. Multi-instance support with web UI. Technically capable but requires you to build and host it yourself.
AlanOgic/odoo-mcp-19 — Odoo 19+ only, JSON/2. Includes a safety layer with risk classification. 5 tools, 27 resources, 13 prompts.
For developers (not ERP data access)
mart337i/odoo-dev-mcp — Different purpose entirely. Helps you build Odoo modules by making 302+ pages of Odoo documentation searchable via AI. Version-aware code generation for Odoo 17-19.
Commercial
CData MCP Server for Odoo — Java/JDBC. Treats Odoo as a SQL database rather than using its native API. Free read-only version. Fits environments already using CData connectors.
Why mobile access matters more than you think
Most people try MCP + Odoo on their laptop and think "nice, this saves me some clicks." The real value shows up when you're away from your desk:
- Standing in a warehouse: "What's the current stock of SKU-4521 across all locations?"
- In a client meeting: "Show me their last 5 invoices and payment status"
- On the train: "Create a lead for the company I just met at the conference"
- Quick check before a call: "What's the margin on quote SO-2847?"
For these scenarios you need something that works on your phone with zero setup. That's the difference between a developer tool and something your whole team actually uses.
Disclosure
I am Rutger from Pantalytics, an Odoo implementation partner in Utrecht, Netherlands. I maintain odoo-mcp-pro, which started as a fork of ivnvxd/mcp-server-odoo. I have tried to make this comparison fair and factual, but I obviously know my own project best. If you spot inaccuracies, please let me know.
Did I miss your project?
If you maintain an Odoo MCP server not listed here, comment below and I will add it to the comparison.