Skip to main content
Glama
io.github.singleflo/odoo-assistant

io.github.singleflo/odoo-assistant

by singleflo

Odoo Assistant MCP 服务器

一个通过模型上下文协议(MCP)实现的 Odoo 虚拟员工。该服务器将 Odoo 的业务逻辑、记录和工作流暴露给大语言模型,使其能够安全地查询、创建、更新和对 Odoo 数据执行操作。

快速开始

1. 安装

直接运行服务器:

uvx odoo-assistant

或将其安装到您的环境中:

uv pip install odoo-assistant

如需从源码安装以进行开发,仍然可行:

uv pip install git+https://github.com/singleflo/odoo-assistant-mcp

2. 配置环境变量

需要设置两个变量;其余配置均会自动发现或存在默认值:

  • ODOO_BASE_URL:您的 Odoo 实例的基础 URL(例如 https://mycompany.odoo.com)。

  • ODOO_API_KEY:Odoo API 密钥(Odoo 14+,在 设置 > 用户 > API 密钥 > 新建 中生成)。不接受账户密码:密钥针对每个用户,可独立设置范围和撤销。

可选配置:

  • ODOO_DB:数据库名称。当实例只提供一个数据库时自动发现;如果提供多个数据库则需要填写——错误信息会列出所有数据库名称。

  • ODOO_USER:登录名。通过密钥发现最多需要额外 59 次往返;如果密钥所有者的 uid 为 60 或更高,则发现失败。设置此变量可跳过探测。

  • ODOO_MCP_MAX_LEVEL:此服务器可执行的最高安全级别,范围为 0 到 4(默认:3)。通过此设置可将服务器设为只读或允许删除——参见选择上限。

  • ODOO_MCP_PROTECTED_HOSTS:此服务器拒绝写入的主机列表(以逗号分隔,默认为空——此包未内置任何主机)。列出的主机仍允许读取;写入需要设置 ODOO_ALLOW_PROD_WRITE=yes 作为有意为之的覆盖。

Related MCP server: mcp-server-odoo

安全层

每次写入和操作在到达 Odoo 之前都会经过动态安全分类器。操作被分为 L0 到 L5 级别:

级别

名称

描述

默认状态

L0

L0_READ

只读查询(search_read、read、search_count)。

允许

L1

L1_WRITE

单条记录写入和创建。

允许

L2

L2_BATCH

影响多条记录的批量写入。

允许

L3

L3_STATE_CHANGE

工作流状态转换(例如确认订单、过账发票)。

允许

L4

L4_DESTRUCTIVE

破坏性操作(例如 unlink、action_cancel、归档)。

阻止

L5

L5_PRIVATE / L5_UNKNOWN

私有方法或未知操作。

阻止

选择上限

ODOO_MCP_MAX_LEVEL 设置此服务器可执行的最高级别。每个值都是累积的——它允许自身级别及以下所有级别:

值

允许的操作

0

仅读取。

1

+ 单条记录写入和创建。

2

+ 超过5条记录的批量写入。

3

默认。 + 确认订单、过账发票、发送邮件。

4

+ unlink、action_cancel、归档。

在选取数值之前,需要了解两种行为:

  • 5 不会解锁 L5。 两个 L5 变体在读取上限之前就会被拒绝。L5_PRIVATE 被拒绝是因为 Odoo 自身会拒绝所有以 _ 开头的方法,因此任何上限都无法传递它;L5_UNKNOWN 被拒绝是因为未经分类的方法,其效果自然未经验证。允许此类方法的途径是将它添加到 safety_layer.py 中的 WRITE_L1/L3/L4 中——通过代码审查,绝不通过配置。

  • 无效值将拒绝启动。 ODOO_MCP_MAX_LEVEL="O" 会引发错误而非回退到默认值,因为默认值允许写入:一个拼写错误绝不能让你得到一个你认为是只读的写入服务器。

上限由人类通过外部方式设定,并在启动时从进程环境读取。运行在此服务器上的模型无法提高它;当调用超过上限时,拒绝信息会指出所需级别,以便代理能够解释操作会改变什么,并将决定权留给你。

请注意,这是此服务器的权限,而非账户的权限。拥有 shell 访问权限的代理始终可以通过直接调用 Odoo 来绕过 MCP 服务器。无论客户端如何都必须保持的限制应归属于 API 密钥所属用户的 Odoo 访问权限中,由 Odoo 服务器强制执行。

Odoo 版本支持

Odoo 14.0 是支持的最低绝对版本,因为此服务器仅使用 API 密钥进行身份验证,而 Odoo 13 及更早版本中不存在 API 密钥。

Odoo 版本

API 密钥

XML-RPC

官方维护(截至 2026年8月)

支持级别/说明

≤ 13.0

否

是

否

不支持。无法使用此服务器进行身份验证。

14.0

是

是

否

协议兼容。未在真实实例上测试。

15.0

是

是

否

协议兼容。未在真实实例上测试。

16.0

是

是

否

协议兼容。未在真实实例上测试。

17.0

是

是

是(至 2026年9月)

协议兼容。未在真实实例上测试。

18.0

是

是

是(至 2027年9月)

主要目标。经过验证并在真实实例上获得完全支持。

19.0

是

是

是(至 2028年9月)

协议兼容。未在真实实例上测试。API 密钥需要描述和有效期(最长 3 个月)。

API 密钥生成路径

要生成 API 密钥,请登录到您的 Odoo 实例并导航至: 偏好设置 / 我的个人资料 → 账户安全 → 新建 API 密钥

传输与弃用说明

客户端会自动检测原生 JSON-2 API 是否可在 /json/2/<model>/<method> 上使用(该接口使用 Authorization: bearer <API_KEY>),如果不可用则回退到 XML-RPC。请注意,XML-RPC 和 JSON-RPC 已在 Odoo 19 中弃用,并计划在 Odoo 22 中移除。

来源

工具和资源

该服务器公开 19 个工具和 2 种资源类型:

工具

  1. search_read:在一次调用中搜索并读取记录(Odoo search_read)。

  2. read_record:按 ID 读取一条记录,始终使用指定字段。

  3. count_records:统计与域匹配的记录数(Odoo search_count)。

  4. instance_overview:汇总已连接实例的信息:版本、公司、各区域量、内部模块、异常。

  5. required_fields:列出 Odoo 在模型上执行 create 之前要求的字段、它将应用的默认值以及现有记录实际如何使用该字段。

  6. create_record:创建记录,当指定 unique_on 时重用现有匹配项。

  7. write_record:向一条记录写入字段值,并报告实际更改的内容。

  8. run_action:运行一个工作流方法并报告它留下的状态。

  9. cancel_record:通过 action_cancel 取消记录,跟随其返回的向导。

  10. notify_user:在记录的讨论区通知用户。默认为内部通知。

  11. create_activity:安排一个活动:唯一带有截止日期的通知。

  12. download_docs:将记录的所有文档保存到磁盘,包括讨论区文件。

  13. generate_pdf:渲染记录的 PDF 并返回保存位置。

  14. list_message_targets:列出哪些人可以接收消息以及在哪里——具有在线/离开/离线状态的内勤用户以及调用者的开放对话。发送前请先询问此工具。

  15. read_conversation:阅读讨论对话,最新优先。

  16. send_direct_message:发送一对一的讨论消息,该消息会实时出现在用户的聊天系统托盘中——无需电子邮件,无论他们的通知设置如何都能收到。

  17. send_channel_message:发布到现有的讨论频道,拒绝包含非员工的房间。

  18. explore_module:通过询问实时实例来发现模块的结构。

  19. list_known_modules:列出此服务器已了解的模块:名称、生成日期、记录数。

工具 10-11(notify_user、create_activity)通知关于一条记录并落在收件箱铃铛中;工具 14-17 是讨论对话,落在聊天系统托盘中。“给用户 X 发消息”是第二种——使用 send_direct_message,而不是 notify_user。

资源

  • odoo://skill:访问 Odoo 助手技能说明。

  • odoo://ref/*:访问已探索模块的生成参考文档。

主机配置示例

以下每个示例仅包含重要内容:两个必需的变量以及上限——决定此服务器能否写入的唯一设置,在人类拥有的文件中可见。数据库和登录名会自动发现,3 是上限的默认值。注意引号:环境值是字符串。

Claude Desktop

将此添加到您的 claude_desktop_config.json:

{
  "mcpServers": {
    "odoo-assistant": {
      "command": "uvx",
      "args": [
        "odoo-assistant"
      ],
      "env": {
        "ODOO_BASE_URL": "https://mycompany.odoo.com",
        "ODOO_API_KEY": "your-api-key-here",
        "ODOO_MCP_MAX_LEVEL": "3"
      }
    }
  }
}

Cursor

将此添加到您的 .cursor/mcp.json 或在 Cursor 设置界面配置:

{
  "mcpServers": {
    "odoo-assistant": {
      "command": "uvx",
      "args": [
        "odoo-assistant"
      ],
      "env": {
        "ODOO_BASE_URL": "https://mycompany.odoo.com",
        "ODOO_API_KEY": "your-api-key-here",
        "ODOO_MCP_MAX_LEVEL": "3"
      }
    }
  }
}

VS Code Copilot

将此添加到您的 VS Code settings.json:

{
  "mcp.servers": {
    "odoo-assistant": {
      "command": "uvx",
      "args": [
        "odoo-assistant"
      ],
      "env": {
        "ODOO_BASE_URL": "https://mycompany.odoo.com",
        "ODOO_API_KEY": "your-api-key-here",
        "ODOO_MCP_MAX_LEVEL": "3"
      }
    }
  }
}

opencode

将此添加到项目中的 opencode.json 或 .opencode/opencode.json,或添加到 ~/.config/opencode/opencode.json 以使该服务器在所有地方可用:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "odoo-assistant": {
      "type": "local",
      "enabled": true,
      "command": [
        "uvx",
        "odoo-assistant"
      ],
      "timeout": 120000,
      "environment": {
        "ODOO_BASE_URL": "https://mycompany.odoo.com",
        "ODOO_API_KEY": "your-api-key-here",
        "ODOO_MCP_MAX_LEVEL": "3"
      }
    }
  }
}

opencode 的结构与上述主机在方式上有所不同,这些差异会导致直接拒绝:键是 mcp(而非 mcpServers),type 是必需的,command 是一个包含程序和其参数的单个数组(没有单独的 args),而环境块是 environment(而非 env)。

请有意设置 timeout。其默认值为 5000 ms,会话的第一次调用需要身份验证,加上对于 instance_overview 来说,需要数十次 XML-RPC 往返——在真实实例上轻松超过五秒。

opencode 在启动时读取一次配置,并且不会热重载,因此编辑后请退出并重新启动。您在此处更改的任何内容(包括上限)仅在下次启动时生效。

ChatGPT(自定义连接器)

要通过自定义连接器将此服务器连接到 ChatGPT:

  1. 前往设置 → 连接器 → 添加连接器。

  2. 输入服务器 URL 或从注册表中选择。

  3. 提示时输入你的 Odoo 凭据。

Hermes

使用 Hermes CLI 添加服务器:

hermes mcp add odoo-assistant \
  --env ODOO_BASE_URL=https://mycompany.odoo.com \
  --env ODOO_API_KEY=your-api-key-here \
  --env ODOO_MCP_MAX_LEVEL=3 \
  --args run odoo-assistant

这些示例省略了可选变量。当实例提供多个数据库时设置 ODOO_DB,设置 ODOO_USER 以跳过 uid 探测,设置 ODOO_MCP_MAX_LEVEL 将上限从默认的 3 更改。

许可证

本项目基于 MIT 许可证授权。详情请参阅 LICENSE 文件。

Available Tools

19 tools
cancel_recordC
Destructive
Inspect

Cancel a record through action_cancel, following the wizard it returns.

Destructive, so the default ceiling refuses it and says what would not.

Inputs: model (required), record_id (required). Returns: result

count_recordsAInspect

Count the records matching a domain (Odoo search_count).

A count is only as honest as its domain:

  • account.move / account.move.line without a move_type filter is refused — it would count invoices, bills, credit notes and journal entries together and match no figure the user has ever seen.

  • A count answers "how many", never "how much". For an amount, read amount_total_signed (company currency) and never amount_total.

  • On a multi-company instance the count differs per company: pass company_ids or you are reporting one company as the whole business.

Args: model: Odoo model, e.g. "crm.lead". domain: Odoo domain. Omit to count everything the model holds. company_ids: Companies to count in, e.g. [1, 2].

Inputs: model (required), domain, company_ids. Returns: result

create_activityAInspect

Schedule an activity: the only notification that carries a deadline.

A chatter note is passive. An activity appears in the assignee's To-Do list and turns overdue when the date passes.

Args: model: the Odoo model, e.g. "crm.lead". record_id: id of the record the activity hangs off. summary: the one-line title the assignee will read. user_id: res.users id of the assignee. days: deadline offset from today, in days. activity_type: substring of an activity type name, e.g. "call". Activity types differ per instance; the first available type is used when this is omitted or matches nothing.

Inputs: model (required), summary (required), user_id (required), record_id (required), +2 more. Returns: result

create_recordAInspect

Create a record, reusing an existing match when unique_on is given.

unique_on is a list of FIELD NAMES taken from values (e.g. ["name", "email"]): they are searched first and the existing id comes back instead of a duplicate. Odoo has no idempotency key, so a create that is retried is simply a second record — this is the only protection there is, and a cold-start run without it produced four identical customers.

Multi-company: put company_id in values. The context decides what is visible, not which company owns the new record.

Inputs: model (required), values (required), unique_on. Returns: result

download_docsAInspect

Save every document of a record to disk — chatter files included.

Returns {"saved": [paths], "skipped": [[name, why]]}. skipped is not noise: a database restored without its filestore keeps the attachment rows and loses the bytes, and an empty result would read exactly like "this record has no attachments".

Args: model: the Odoo model, e.g. "account.move". record_id: id of the record whose documents to fetch. dest_dir: directory to write the files into. Defaults to this platform's temporary directory — "/tmp" does not exist on Windows.

Inputs: model (required), record_id (required), dest_dir. Returns: result

explore_moduleBInspect

Discover a module's structure by interrogating the live instance.

Args: module_name: Module to explore, e.g. "helpdesk". Must be a module slug, since it names the reference file on "generate"; ignored on "list". action: "generate" (the default) writes the reference document, "list" ranks what is worth exploring. models: Comma-separated models for a module the script does not know, e.g. "superchat.message,superchat.template". Defaults to the script's own grouping for module_name.

Inputs: module_name (required), action, models. Returns: result

generate_pdfAInspect

Render the PDF of a record and return where it was saved.

An already rendered PDF is reused. Otherwise the model's own print/send wizard produces it, and that wizard can also SEND the document — which is why this is gated on action_send_and_print (L3_STATE_CHANGE) rather than as a plain read.

Args: model: the Odoo model, e.g. "account.move". record_id: id of the record to print. dest_dir: directory to write the PDF into. Defaults to this platform's temporary directory — "/tmp" does not exist on Windows.

Inputs: model (required), record_id (required), dest_dir. Returns: result

instance_overviewAInspect

Summarise the connected instance: version, companies, volumes per area, in-house modules, anomalies.

The profile is built from the instance this server is CONNECTED to, and cached per instance — census.profile_path() keys it on the live client, not on an environment variable. That distinction is the whole point: with two instances profiled on one machine, choosing by ODOO_DB (which is discovered now, so often unset) once fell through to "the first file on disk" and reported a neighbour's numbers as this instance's, with no error and a perfectly plausible report.

First call against a new instance builds the profile, which costs a second or so; every later call is free. Pass refresh=True after the instance has changed — the report carries the timestamp it was taken.

When drilling into these figures, the two rules that keep them meaningful: filter account.move by move_type, and sum amount_total_signed, never amount_total.

Args: refresh: rebuild the profile from the instance instead of reusing it.

Inputs: refresh. Returns: result

list_known_modulesAInspect

List the modules this server has learned: name, generation date, records.

Inputs: no named parameters. Returns: result

list_message_targetsAInspect

Who can be messaged and where — ASK THIS BEFORE SENDING ANYTHING.

Two lists in one call, because an agent that cannot see the roster invents ids:

  • users: the internal, active users, each with im_status — 'online', 'away' (idle 30 minutes) or 'offline'. Presence is worth reading first: a Discuss message is delivered either way, but "offline" tells you nobody is going to answer right now.

  • conversations: the ones the sender already belongs to and has not archived, with channel_type — 'chat' is a 1-to-1, 'group' is a private multi-party, 'channel' is a room that may hold the whole company. members and unread are there so a broadcast is a deliberate choice rather than a surprise.

Use send_direct_message for a person and send_channel_message for a conversation in this list. Neither of them is the tool for annotating an invoice or an order — that is notify_user.

Inputs: no named parameters. Returns: result

notify_userAInspect

Write a note on a record's chatter and notify the users you name.

Both subtypes post a message that IS VISIBLE in the record's chatter. The difference is who it reaches beyond the people you name.

Args: model: the Odoo model, e.g. "sale.order". record_id: id of the record to write on. message: the body. Send PLAIN TEXT: Odoo escapes anything that arrives over RPC, so "x" is displayed as the literal characters <b>x</b>, not as bold — there is no way to pass real markup through this call, and newlines survive but are not turned into line breaks. Write the note as prose. user_ids: res.users ids to notify. They are notified each through their OWN Odoo setting, inbox or email, so naming someone is not a promise that no mail leaves. subtype: where the message lands.

    | subtype   | visible in the chatter | emails a customer |
    |-----------|------------------------|-------------------|
    | "note"    | yes, internal users    | never             |
    | "inbox"   | NO — notification only | never             |
    | "comment" | yes, everyone          | **YES**           |

    "note" posts `mail.mt_note` and is the default: measured on a real
    order it produced one inbox notification and zero emails.
    "inbox" goes through `message_notify`, which Odoo documents as the
    path for "messages that should not be displayed on a document" —
    the person is notified, the record keeps no trace. "comment" posts
    `mail.mt_comment` and is refused while an external follower
    exists, unless force=True.
force: post the comment anyway, knowing those people get an email.

Inputs: model (required), message (required), user_ids (required), record_id (required), +2 more. Returns: result

read_conversationAInspect

Read what was said in a Discuss conversation, newest first.

This is how you answer "what did they write to me" or "what is going on in that channel". list_message_targets gives you the channel_id and says how many messages are unread.

Reading does not mark anything as read: the unread counter belongs to the member record and only the user's own client clears it.

Args: channel_id: the Discuss channel, from list_message_targets. limit: how many recent messages to return.

Inputs: channel_id (required), limit. Returns: result

read_recordAInspect

Read one record by id, always with named fields (writing.md pattern 12).

Omitting fields asks for a short list of state fields — never for all of them: that read is slow at best and fails at worst.

account.move and account.move.line are refused here, because the structural guard wants a move_type filter and this tool has nowhere to put one. Use search_read with [["id", "=", <id>], ["move_type", "=", "out_invoice"]] instead.

And never add up amount_total across records — it is in the record's own currency. amount_total_signed is the company-currency twin to sum.

Args: model: Odoo model, e.g. "sale.order". record_id: The record's database id. fields: Field names to read. Omit for the usual state fields.

Inputs: model (required), record_id (required), fields. Returns: result

required_fieldsAInspect

List the fields Odoo demands before it will accept a create, with the default it would apply and how existing records actually use it.

Ask this BEFORE create_record on a model you have not written to in this session. The answer is read from the live instance — fields_get plus default_get — never from a table in this file, so a model customised in-house reports its own requirements.

The dangerous required field is the one that already carries a default: the create succeeds without you naming it and the record lands wherever the default points, with no error to notice. crm.lead.type is the standing example — Odoo defaults it to 'lead', and on an instance that works its pipeline as opportunities that record goes straight to a menu nobody opens. That is why the live distribution is printed beside each default.

Args: model: Odoo model, e.g. "crm.lead".

Inputs: model (required). Returns: result

run_actionA
Destructive
Inspect

Run a workflow method and report the state it left behind.

The level follows method: confirming or posting is a state change, cancelling or unlinking is destructive and refused unless the server's ceiling was raised deliberately.

Two behaviours come from the Writer and are worth knowing: a returned dict carrying res_model is a wizard to follow rather than a result, and a transition is one-way — calling it twice raises instead of doing nothing.

Inputs: model (required), method (required), record_ids (required). Returns: result

search_readAInspect

Search and read records in one call (Odoo search_read).

Two pitfalls this tool cannot fix for you:

  • account.move and account.move.line mix customer invoices, vendor bills, credit notes and raw journal entries. A domain without move_type is refused — add ["move_type", "=", "out_invoice"] (or in_invoice, out_refund, in_refund) so the answer matches what the user sees on screen.

  • NEVER sum amount_total: it is expressed in each record's own currency, and eight foreign-currency invoices once inflated a total 11,9×. Ask for amount_total_signed instead — any field with a _signed twin is stored in company currency, and the twin is the one to add up.

Args: model: Odoo model, e.g. "sale.order". domain: Odoo domain, e.g. [["state", "=", "sale"]]. fields: Field names to return. Name them: the default asks for every field, which is slow and can fail to serialise on wide models. limit: Rows to return. Hard-capped at 200. offset: Rows to skip — how to page past a truncated result. company_ids: Companies to read from, e.g. [1, 2]. On a multi-company instance, omitting this reports one company as the whole business.

Inputs: model (required), domain (required), limit, fields, +2 more. Returns: result

send_channel_messageAInspect

Post to an EXISTING Discuss channel — everyone in it sees this.

The channel is never created here: list_message_targets shows the ones that exist, and posting to a room of the wrong size is not recoverable by deleting the message afterwards.

Members who are not employees of this instance — portal users, guests — are named in a refusal rather than written to, the same rule notify_user applies to external followers. Nothing is posted in that case.

Args: channel_id: from list_message_targets. message: the body, plain text or simple HTML.

Inputs: message (required), channel_id (required). Returns: result

send_direct_messageAInspect

Send a 1-to-1 Discuss message that appears in the user's chat systray.

This is the tool for "tell X", "message X", "warn X". It opens the private chat with that user — reusing the existing one, channel_get matches on the exact pair — and posts there. The bus pushes it in real time and it persists, so a recipient who is offline finds it on their next login.

It reaches them whatever their notification setting says, and sends no email at all. That is the difference from notify_user, which follows the recipient's preference and lands in the Inbox bell instead.

Args: user_id: res.users id of the recipient — from list_message_targets. message: the body, plain text or simple HTML.

Inputs: message (required), user_id (required). Returns: result

write_recordA
DestructiveIdempotent
Inspect

Write field values to one record and report what actually changed.

Writing the value a record already holds succeeds and changes nothing; only the before/after comparison tells that apart from a real update, so that comparison is the answer.

Setting active to False archives the record — the same visible outcome as deleting it — and is classified destructive rather than as a plain write.

Inputs: model (required), values (required), record_id (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct Odoo operation: reading, searching, counting, creating, writing, workflow actions, messaging, module exploration, etc. While messaging has multiple tools (notify_user, send_direct_message, send_channel_message), their descriptions clearly differentiate by context (record chatter, 1-to-1 chat, channel). No overlapping purposes remain ambiguous.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., search_read, create_record, list_message_targets). The naming is predictable and intuitive, with verbs like read, create, write, send, list, and explore clearly indicating the action.

    Tool Count4/5

    With 19 tools, the server covers a broad set of Odoo capabilities (CRUD, workflow, messaging, file handling, module introspection). While slightly above the typical 3-15 recommended range, the count is justified by the complexity of the ERP domain and each tool serves a distinct purpose without redundancy.

    Completeness4/5

    The tool surface covers essential CRUD operations, workflow actions, messaging, document handling, and instance/ module exploration. However, there is no dedicated delete tool (only cancel for specific workflows) and no bulk update or file upload tool. These minor gaps are workable but prevent full lifecycle coverage.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      Not graded
      maintenance
      An MCP server that enables AI assistants to interact with Odoo ERP apps like Inventory, CRM, Sales, and Manufacturing. It allows users to read, create, and manage Odoo records and workflows using natural language commands.
      25
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An extensible MCP server that integrates Odoo with LLMs to enable querying and managing business data like partners, quotations, and sales orders. It supports custom tool registration and multiple transport protocols for both local and remote communication.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects AI assistants to Odoo ERP instances via the built-in XML-RPC API without requiring any additional addons. It enables users to search, create, update, and manage Odoo records and models through natural language.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to interact with Odoo ERP, allowing natural language queries, record creation, updates, and deletions.
      LGPL 3.0