Odoo 14-18 (JSON-RPC)
Odoo ERP 14 to 18 over the classic JSON-RPC endpoint: search, read, create and update any model, plus partners, sales orders, invoices and products. For Odoo Online, Odoo.sh and self-hosted Odoo older than 19 (works on 19 too). API key + user id.
7 天免费 · 无需信用卡 · EU 托管
问 Odoo 任何事
通过 AnythingMCP 对 Odoo 14-18 (JSON-RPC) 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 OdooClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Odoo 14-18 (JSON-RPC)。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
配置 Odoo 14-18 (JSON-RPC)
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
Which Odoo connector? This one is for Odoo 14 to 18 (and works on 19 too). It talks to Odoo's classic JSON-RPC endpoint /jsonrpc. For Odoo 19 and newer, the "Odoo" connector (JSON-2 API) is the simpler choice: it needs no user id. Your version is shown at the bottom of Settings.
What you need (four values)
ODOO_URL: the address of your Odoo, scheme and host only, e.g.https://erp.example.comorhttps://mycompany.odoo.com. Not the address of a page inside Odoo: nothing after the host, no/web, no?db=or#action=.ODOO_DB: the database name. On Odoo Online it is usually the subdomain. On your own server it is the name shown on the database selector, or the value after?db=in the address bar.ODOO_API_KEY: in Odoo open your user menu → Preferences (Odoo 14/15: My Profile) → Account Security → New API Key. On Odoo 18 and later the dialog also asks for a Duration: choose Persistent Key (offered to administrators) or the longest duration offered (up to 3 Months for other users). It preselects 1 Day, and such a key stops working the next day with Access Denied. Odoo shows the key once. If the Account Security tab or the API key button is missing, turn on developer mode (Settings → Activate the developer mode). The key replaces your password for API calls; your login password itself also works but is not recommended.ODOO_UID: the numeric id of the Odoo user the key belongs to. Open Settings → Users & Companies → Users, open that user, and read the number afterid=in the address bar (e.g....#id=7&model=res.users→7).
The key, the user id and the database must belong together: a key of user 7 with ODOO_UID=2 is refused.
Errors: Odoo answers JSON-RPC errors inside an HTTP 200 with an error object. AnythingMCP raises them as errors carrying Odoo's own message: Access Denied (wrong or expired key, user id or database), Invalid field 'x' on model 'y' (field names differ between versions), Record does not exist.
Domains are Odoo's query language. A domain is a list of triples: [["state","=","sale"],["amount_total",">",1000]], implicitly AND-ed. | and ! prefix operators express OR and NOT.
Always pass fields to odoo_search_read and odoo_read: Odoo models have hundreds of columns. Start with odoo_fields_get to see what exists; field names differ between Odoo versions (e.g. mobile on res.partner is gone in 19).
Permissions follow the user. The key inherits its owner's access rights and record rules. A restricted user sees fewer rows, not an error.
Self-hosted: on AnythingMCP Cloud the instance must be reachable from the public internet with a valid TLS certificate. On an internal host, self-host AnythingMCP on the same network and add the host to SSRF_ALLOWED_HOSTS.
Writes: odoo_create, odoo_write and odoo_call_method change the live database, and Odoo's automations fire as if a person had done it.