Skip to main content
Glama
SaintsFlow

odoo-mcp

by SaintsFlow

odoo-mcp

An MCP server for Odoo. It gives an LLM agent read and write access to partners, sales orders, stock levels and invoices in an Odoo instance.

Status: early. The tool list below is the plan. Not all of it works yet.

Why

Odoo is a full ERP with a wide API, which makes it hard for an agent to use. Its external API is XML-RPC with generic search_read and execute_kw calls, so the agent would need to know model names, field names and domain syntax. This server exposes a small number of named tools instead, each one covering a task a person would actually ask for.

Odoo Community runs in Docker with demo data, so the whole thing can be tried without any real system.

Related MCP server: MCP Server for Odoo

Tools

Tool

What it does

search_partners

find customers and suppliers

get_sales_order

read an order with its lines and status

create_sales_order

create a draft order for a partner

confirm_sales_order

confirm a draft order

get_stock

current quantity on hand for a product

list_invoices

invoices for a partner, filtered by state

Quick start

docker compose up -d odoo db    # Odoo Community with demo data
cp .env.example .env
docker compose up mcp

Odoo takes about a minute to initialise its database on first start.

How it works

The server connects to Odoo over XML-RPC. Each tool builds the domain and the field list itself, so the agent never sees Odoo internals. Results are trimmed to the fields that matter and returned as flat records.

Design decisions

Named tools, not a generic query tool. A single run_query tool would be easier to write and much worse to use. Named tools carry their own validation and make it obvious what the agent is allowed to do.

Read and write are separated. Write tools are marked in the schema so the client can require confirmation.

Errors are translated. Odoo raises faults with long tracebacks. The server extracts the message and returns it in a form the agent can act on.

What is not here yet

  • pagination and result limits

  • multi-company support

  • tests against a seeded Odoo instance

License

MIT

Install Server
A
license - permissive license
Not graded
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to interact with Odoo ERP systems through natural language, allowing users to search, create, update, and manage business records like customers, products, and invoices across any Odoo instance.
    1
    Mozilla Public 2.0
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to interact with Odoo ERP as the authenticated user, with tools for discovery, planning, and mutations bounded by user permissions.
    34
    37
    2
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to fully interact with Odoo ERP instances over XML-RPC, supporting read and write operations on any model without requiring Odoo module installation.
    4
    AGPL 3.0

View all related MCP servers

Related MCP Connectors

  • Odoo ERP for AI agents: hosted OAuth endpoint, gated writes, one endpoint for every instance.

  • Give AI agents the LinkedIn tools to find, qualify, engage, and follow up with prospects.

  • Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SaintsFlow/odoo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server