Why use doo.mcp when Odoo already has a Claude MCP

If your Odoo database can already talk to Claude over MCP, the fair question is why add another product. The two connections do different jobs. One sits with the employee who already has a login. The other sits with the shopper who does not.

What an Odoo MCP is for

An Odoo MCP server exposes tools to an AI client such as Claude. The person using it is on your team. They installed the client, they hold a key, and the tools run against the database they are allowed to open. That is a useful way for staff to ask questions and take actions without clicking through every form.

A shopper on your website is not that person. They should not receive a general set of Odoo tools, and they should not need Claude installed to buy a pair of shoes.

What the storefront does instead

The eCommerce Agent is the live product for an Odoo store. A shopper describes what they want. The agent searches the real catalog, checks stock, and adds to the cart. On your website, that cart is the shopper’s real website cart, so the bag in the header stays in step with the chat.

The step-by-step version, with a comparison against Odoo Live Chat and Odoo 19’s built-in AI, is in the AI chatbot for Odoo guide.

Before anything is placed, the shopper sees items, taxes, and totals and chooses confirm, change, or cancel. Card payment happens on your store’s own payment flow. On WhatsApp, which is part of a paid eCommerce subscription, the shopper receives a payment link. doo.mcp does not collect the card.

Prices and stock come from calls to your store. The agent is instructed never to state those numbers from memory. When a shopper asks for a person, the AI pauses and your team takes the conversation from a shared inbox. A handoff left open for about two hours returns to the AI.

The commerce MCP is read-only on purpose

Paid eCommerce plans also expose an MCP endpoint for Claude and Cursor. It can search products, read details, and check stock. It cannot add to a cart. Cart and checkout run on the website widget, WhatsApp, and the mobile API. A read-only catalog tool is safe to hand to an assistant on your team. A public checkout flow is a different surface, with a review step and your payment page.

The staff path is a separate agent

The Odoo Agent, in beta, is the closer match to a Claude MCP for employees. It searches, creates, and updates records, runs actions, and can produce a PDF report. It acts as the person who asked, so that person’s access rights and record rules apply. Requests for passwords, API keys, mail servers, access rules, and security groups are refused before they are sent to Odoo. Every action is written to an audit log with the person, the tool, and the record.

Setup, MCP, and the price are in the Odoo AI agent guide.

You can reach it from the dashboard, or from Cursor and Claude with your MCP key plus that employee’s Odoo login. It is its own subscription, starting at $49 a month.

• Use Odoo’s own MCP when an employee wants Claude on the database they already administer.
• Use the eCommerce Agent when a shopper should search, cart, and check out on your site.
• Use the Odoo Agent when staff need a hosted assistant that still obeys each person’s Odoo rights.