How doo.mcp differs from a generic MCP server

MCP is an open way for a client such as Claude or Cursor to call tools. Anyone can stand up a server that speaks it. A comparison that stops at “we also speak MCP” misses the product. The protocol is the plug. doo.mcp is what is plugged in, who is allowed to use it, and where the answer shows up.

A server is an endpoint. A workspace is an account.

A generic MCP server is something you host, secure, and keep running. You invent the key scheme, the logs, and the way a second customer is kept out of the first customer’s data.

A doo.mcp workspace is created at signup. It holds the Odoo connection, the widget, the conversations, the trained documents, and the usage for that tenant. Connector secrets are encrypted before they are stored. A request is bound to one workspace and cannot switch to another customer’s data mid-call. Workspace login, billing, and settings keep working when the store is briefly unreachable.

The same catalog, several callers

On a generic commerce MCP, the caller is usually a developer’s AI client. On doo.mcp, through the eCommerce Agent, the caller can be a shopper in the website widget, a shopper on WhatsApp, a mobile app using the session API, your own backend over REST, or Claude and Cursor over MCP.

If the caller is a shopper on an Odoo store, the AI chatbot for Odoo guide shows the setup.

Those surfaces are not equal, and they should not be. The public widget can build a cart and open checkout. The MCP endpoint for Claude and Cursor is read-only: search, product details, and stock, on paid eCommerce plans. REST exposes the tools to your own backend with your MCP key. The mobile API can run the full chat, or answer questions and hand checkout to your native cart.

What a protocol server leaves to you

• A website widget that shares the shopper’s real Odoo cart
• A review step before an order is created, and payment on your store
• A shared inbox and human handoff
• A store FAQ, up to 40 documents, beside live catalog tools
• Monthly allowances per agent, a permanent free plan, and a published price for each paid agent

If the only requirement is “let our developers query Odoo from Cursor,” a raw MCP server can be enough. doo.mcp is the product when the caller is a customer, when you want the hosting and the metering done, or when the same store connection should also answer on the website and on WhatsApp.