io.github.tuanle96/mcp-odoo

It requires ODOO_URL, ODOO_DB, ODOO_USERNAME, and ODOO_PASSWORD. The username and password are sensitive business credentials that can access the target Odoo instance; the materials do not describe storage, encryption, or least-privilege handling, so standard leakage or misuse risk remains.

No fixed third-party remote endpoint is declared, but the required ODOO_URL indicates it will connect over the network to a user-configured Odoo service and may transmit queries, business records, or write requests. There is no clear red flag showing exfiltration to unrelated or unknown domains.

The system flags indicate it executes code or starts a local process, which is a normal characteristic of MCP tools. The available materials do not show requests for clearly excessive system privileges unrelated to Odoo integration, so this alone does not justify a high-risk rating.

The description mentions schema discovery, access diagnostics, multi-instance routing, and gated writes, implying it may read instance metadata, access status, and business data, and perform controlled writes. The materials do not specify exact models, fields, files, or permission boundaries, so it should be assumed to have access equivalent to the configured Odoo account.

It comes from an official registry, has an auditable open-source repository, and was updated within the last year, all of which reduce risk. However, the lack of a README, no declared license, and very low community adoption (0 stars) limit documentation and external validation, so supply-chain confidence should remain cautious.