Odoo Gemini integration with allowed_tools, not a custom plugin.

What Google documents

Remote MCP on the Gemini API is Streamable HTTP. Pass allowed_tools so delete is not callable just because the server advertised it. SSE is not this path. Clicks: connect Odoo to Gemini.

One Odoo MCP server can still serve Gemini, Claude and ChatGPT. That is the point of MCP.

ERP-sized allow lists

search_overdue_invoices is a capability. execute_any_odoo_method is an incident. allowed_tools is the client half; the Odoo user is the server half.

Same on Odoo 18 and Odoo 17 — the Odoo API generation changes, the allow-list does not.

Online

External MCP to Online still hits the Custom-plan API gate. In-Odoo MCP on Community 18/19 can skip it. Odoo Online.

allowed_tools as a change-control item

When someone adds confirm_order to the MCP server, Gemini will not call it unless you also add it to allowed_tools — if you configured that list. Keep the list in git next to the server. Review it like an ACL, not like a demo flag.

If you cannot show the list in an audit, you do not have a Gemini integration. You have a hope.

HTTP details that bite

Streamable HTTP, not SSE. Timeouts: ERP searches can be slow; keep tools to indexed domains (customer name, invoice number), not “scan all stock.move.” TLS must match what Gemini’s runtime can reach — a laptop ngrok for a board demo is not the production URL.

Official documentation

• Gemini: function calling and remote MCP
• Model Context Protocol
• Odoo 19 External API