How to connect Odoo to Gemini using MCP.

Gemini can attach remote MCP servers. You provide the URL; you can restrict the tools the agent may call. That is a better ERP default than “here is the whole database.”

Architecture: Odoo → Odoo API or in-process ORM → Odoo MCP server → remote MCP → Gemini.

What can Gemini do with Odoo?

Whatever you expose: customers, sales, CRM, inventory, accounting, products, purchases, projects, reporting. The model chooses a tool from that list. It cannot invent a unlink you did not publish.

Useful allow-list: search_customers, read_sales_orders, search_products. Leave out delete_record, update_invoice, confirm_order until there is a human in the loop.

Connect Gemini to Odoo

1. Deploy the MCP server and put it on HTTPS.
2. Authenticate to Odoo as a dedicated user. On Odoo 19, JSON-2 with a bearer API key.
3. Make the MCP endpoint reachable from Gemini.
4. Set allowed_tools to the read surface only.
5. Test: customers idle 90 days, today's sales, unpaid invoices over a threshold, products below reorder.

Google documents remote MCP over Streamable HTTP, including an allowed_tools allow-list. SSE servers are not supported. If your server only speaks another transport, Gemini will not see it.

Why MCP instead of a custom Gemini integration?

Without MCP you build a Gemini-only adapter. With MCP the same Odoo tool surface can serve Gemini, ChatGPT, Claude and other MCP-compatible agents. One controlled integration, several clients.

Security is still Odoo permissions plus the tool allow-list. JSON-2 applies the authenticated user's rights. Never assume the model should have admin. Free Odoo MCP · try live.

Gemini client vs JSON-2 back end

Remote MCP, Streamable HTTP, and allowed_tools are Gemini-side controls. They do not replace Odoo access rights. A tool Gemini is allowed to call can still 403 if the bot user cannot read the model.

The matching stack article is Gemini + JSON-2 + MCP. Use that when the question is “what does the server POST to Odoo 19?” Use this when the question is “how do I attach Gemini?”

One MCP server should serve Gemini and the other MCP-compatible clients. Duplicating Odoo credentials per vendor is how keys leak.

Treat allowed_tools as a second lock, not the only lock

If Gemini’s allow-list is “all tools the server exposes,” you have one lock: the server. If the server also exposes a generic ORM tool, you have zero effective locks.

Set allowed_tools to the same names you would write on a whiteboard for the team. When you add a write tool on the server, it should stay off Gemini until you add it here too — on purpose, on a date, with a person named.

Then test with a known stock figure or invoice count. Gemini summarizing the wrong company in a multi-company database is a record-rule miss, not a model-quality issue.

Official documentation

• Gemini API: function calling and remote MCP
• Model Context Protocol
• Odoo 19 External API (JSON-2)