Odoo 18 Gemini integration.
Gemini’s allowed_tools still matter on 18. The Odoo side is XML-RPC or an in-Odoo MCP module. JSON-2 is a 19 document.
Client vs ERP version
Gemini: Streamable HTTP, allowed_tools, not SSE. Odoo 18: external API without JSON-2. Odin module on 18 uses the ORM.
How-to: connect Odoo to Gemini. Hub: Odoo MCP for Odoo 18.
Allow-list first
On 18 it is even easier to wrap “all XML-RPC methods” and call it MCP. Don’t. Name the tools. Exclude unlink and confirm. Security.
allowed_tools on an XML-RPC server
XML-RPC can look like “one execute method.” If your MCP server wraps execute, Gemini’s allow-list cannot save you — the dangerous power is inside one tool. Split tools. Then allow-list the split.
That is the 18-specific footgun. 19 JSON-2 with model/method in the URL makes it slightly harder to hide a god tool. Slightly. Still split.
Latency
18 XML-RPC round trips are chatty. Batch search_read in the MCP tool, do not let Gemini loop 50 partner ids as 50 calls. Timeouts will look like “Gemini is flaky.”
Official documentation
FAQ
SSE on Gemini + 18?
No. Streamable HTTP.
JSON-2 on 18?
No.
Odin on 18?
Yes.
Keep going
Start read-only. Ask a real question.
Sandbox on sample Odoo 19 data, or we put MCP on your instance.