A build-to-order Model Context Protocol (MCP) server that lets AI assistants read from and act inside your Odoo instance safely. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 environment. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
App-Manifest
Auf Ihren Workflow zugeschnitten
A build-to-order Model Context Protocol (MCP) server that lets AI assistants read from and act inside your Odoo instance safely. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 environment.
Keine Selbsteinrichtung — eine funktionierende App, die von ECOSIRE erstellt, installiert und betreut wird.
Starten Sie mit einem einmaligen Entwicklungspreis. Den Umfang legen wir beim Kickoff gemeinsam fest.
ECOSIRE erstellt, konfiguriert und installiert sie auf Ihrem Odoo.
Sie gehen in etwa 2–4 Wochen live, mit einem Support-Zeitraum nach dem Launch.
Teams that run Odoo increasingly want to ask an AI assistant plain-language questions ("which sale orders are stuck in sent past their commitment date?", "draft a purchase order for the low-stock parts", "summarize this quarter's helpdesk backlog") and have the assistant act against live company data instead of a stale export. Out of the box, Odoo exposes an XML-RPC/JSON-RPC API, but that API speaks in raw model names, field lists, and integer IDs. It has no notion of an AI tool contract, no permission-scoped tool catalog, and no structured way to describe "here is what you may read and what you may do." Bolting a general-purpose assistant onto that raw surface either leaks everything the connecting user can see, or forces every prompt to hand-roll RPC calls. That gap, a safe and described and action-aware bridge between an AI client and Odoo, is what this build closes.
We build a Model Context Protocol (MCP) server tailored to your Odoo deployment. On the Odoo side we ship a proper addon (__manifest__.py, an mcp.tool and mcp.audit.log model layer built on models.Model with fields, compute methods and @api.depends, plus ir.model.access.csv and record rules) that defines exactly which models, fields, and operations are exposed as MCP tools and resources. The MCP server process itself authenticates to Odoo over JSON-RPC/XML-RPC using a dedicated technical user whose access rights are the real enforcement boundary, so an assistant can never do more than that user is permitted to do. Read tools map to search_read with server-side domains and field allowlists; write tools (create quotation, log an activity, post an internal note) are wrapped so they validate inputs, respect record rules, and write an audit row before committing. Every tool is described with a typed schema the AI client discovers at connection time, so the assistant knows the arguments, defaults, and return shape without guessing.
The server runs alongside Odoo (stdio for a local desktop assistant, or an HTTP/SSE transport behind your reverse proxy for team use) and can drive any MCP-compatible AI client. We can expose curated resources (a company's product catalog, open pipeline, current stock) and curated actions (draft SO/PO, create CRM lead, schedule an activity, trigger an existing automated action or server action). Odoo QWeb reports can be surfaced as downloadable tool outputs, and Enterprise-only capabilities (for example studio-defined models or subscription objects) are wired only when your edition supports them, with a Community-safe fallback path documented where it differs.
Because this is build-to-order, we start with a short scoping call to agree which models, fields, and actions belong in your tool catalog, your Odoo edition and version (17.0, 18.0, or 19.0), and which AI client(s) will connect. From confirmed scope, typical delivery is two to four weeks, ending with UAT on a staging database and a supported go-live. Pricing starts from $249 (indicative, single-company base scope); the number of exposed models and write actions, multi-company record-rule complexity, custom integrations, and whether the transport must be hardened for external/team access increase the quoted scope. You receive a fixed quote after the scoping call, never a surprise charge.
Wants staff to ask an AI assistant for live answers (stuck orders, low stock, overdue activities) and take routine actions without opening five menus, while keeping every read and write inside Odoo's existing permission model.
Needs a governed, auditable bridge rather than an assistant wired directly to raw XML-RPC. Cares about the technical user's access rights, record rules, audit logging, and a clear way to add or revoke exposed tools over time.
Wants their chosen AI assistant to actually work with company data in Odoo, delivered and supported, without hiring an in-house team to build and maintain an MCP integration from scratch.
Needs a reliable, documented MCP layer they can hand to a client, with a git repo, clear tool schemas, and edition-aware behavior across Odoo 17/18/19 for Community and Enterprise deployments.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| AI/MCP tool contract | Typed MCP tools with discoverable schemas per exposed capability | Whatever your developer hand-builds and maintains | Generic connector, often fixed tool set you can't reshape | |
| Permission enforcement | Dedicated technical user bounded by `ir.model.access.csv` and record rules | Depends entirely on how carefully it's coded | Often broad access tied to one API user | |
| Audit trail of AI actions | Every read/write logged in an `mcp.audit.log` model | Only if separately built | Rarely included or limited | |
| Write actions | Curated, validated tools (draft SO/PO, lead, activity, note) | Buildable but you own the validation and edge cases | Usually read-focused or coarse writes | |
| Fit to your models | Tool catalog tailored to your exact models and fields | Fully custom, but you fund and maintain it | One-size template, limited configurability | |
| Version/edition coverage | Odoo 17/18/19, Community and Enterprise, differences documented | Whatever you target and keep updating | Often single-version, upgrades lag | |
| Delivery and support | Scoped, built, UAT on staging, training, support window, git handover | You manage timeline, testing, and support | Install yourself; support varies by vendor | |
| Total cost of ownership | Indicative from $249, fixed quote after scoping | Higher; full dev plus ongoing maintenance | Low sticker price, limited fit and support |
This is a build-to-order service, not an instant download. After a short scoping call to confirm your tool catalog, Odoo edition/version, and AI client, typical delivery is two to four weeks from confirmed scope, ending with UAT on staging and a supported go-live.
Pricing starts from $249 as an indicative single-company base scope. The final number depends on how many models and write actions you expose, multi-company complexity, and transport hardening. You receive a fixed quote after the scoping call, so there are no surprise charges.
Every engagement includes a post-go-live support window for fixes and configuration adjustments. Because you receive the full source and git repository, your team can extend it independently, and we can quote ongoing support or version upgrades (for example moving from Odoo 18.0 to 19.0) separately.
No. The server authenticates as a dedicated technical user whose `ir.model.access.csv` rights and record rules are the real boundary. Only the models, fields, and actions we explicitly expose become tools, each write is validated and audit-logged in an `mcp.audit.log` model, and the AI client never sees your Odoo credentials.
We support Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. Where a capability depends on Enterprise-only modules, we document the difference and provide a Community-safe path where one exists.
Any client that speaks the Model Context Protocol. We deliver stdio transport for a local desktop assistant or an HTTP/SSE transport behind your reverse proxy for team access, plus a configuration reference for connecting your chosen MCP-compatible client.
No. We build and validate against a staging copy of your database, run UAT there with a documented rollback plan, and only then deploy to production, so your live data is never the test bed.
A build-to-order Model Context Protocol (MCP) server that lets AI assistants read from and act inside your Odoo instance safely. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 environment.