Provides tools to interact with Odoo ERP, including sales orders, invoices, inventory, contacts, and custom reports, with per-user permission enforcement, write-confirmation safety, and audit logging.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Odoo MCP Connector list my pending sales orders"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Production-grade Odoo add-ons that expose Odoo business functionality to Claude (and other MCP-compliant clients) as a remote Model Context Protocol (MCP) connector over HTTP, with OAuth 2.1 auth, per-user Odoo permission enforcement, write-confirmation safety, and full audit logging.
See PLAN.md for the full architecture and delivery plan.
addons/mcp_server — core: MCP protocol engine, OAuth 2.1 provider,
generic model access engine, confirmation-token workflow, audit log.
addons/mcp_server_sales — Sales orders/quotations tools.
addons/mcp_server_purchase — Purchase RFQ/orders tools.
addons/mcp_server_accounting — Invoicing/Accounting tools.
addons/mcp_server_inventory — Inventory/Stock tools.
addons/mcp_server_contacts — Contacts/Partners tools.
addons/mcp_server_reports_designer — expose GTECH Report Designer
(reports.designer) custom reports as short-lived PDF download links.
Related MCP server: foggy-odoo-bridge
Core module mcp_server implemented (PLAN.md Phases 1–4):
MCP Streamable HTTP transport (JSON-RPC 2.0) at POST /mcp, DELETE /mcp
session teardown, pinned protocol version 2025-06-18 (no batching).
Two error channels: protocol errors as JSON-RPC error; tool errors as
successful results with isError: true.
OAuth 2.1 AS + Resource Server: DCR, Authorization Code + PKCE (S256),
refresh-token rotation, RFC 8707 resource-indicator binding, RFC 7009 revoke,
.well-known metadata. Secrets hashed at rest.
Import-time tool/resource registry for domain add-ons.
Generic model engine (odoo.*) gated by the mcp.model.access allowlist plus
real Odoo ACL/record rules.
Propose → confirm workflow for all writes (single-use, user-bound tokens).
Full audit log with pivot/graph views and sensitive-action alerting.
Admin UI (Settings + dedicated MCP app menu) and cron GC jobs.
Test suite (addons/mcp_server/tests/) covering JSON-RPC, schema, protocol
error channels, confirmation flow, generic engine, OAuth/PKCE, and audit.
Run tests:
odoo -d <db> -i mcp_server --test-enable --stop-after-initDomain add-ons (mcp_server_sales, _inventory, _contacts) follow the same
template; mcp_server_accounting is implemented (PLAN.md Phase 5).
This server cannot be deployed
Odoo ERP for AI agents: hosted OAuth endpoint, gated writes, one endpoint for every instance.
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
Governed property-management MCP: portfolio, leasing, accounting, maintenance, OAuth 2.1.
Headless API-first double-entry accounting & bookkeeping engine. 84 MCP tools over HTTP.
