mcp-server-odoo — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Read and modify Odoo ERP records via MCP

What we know

Model Context Protocol (MCP) server that enables AI assistants to securely interact with Odoo ERP systems through standardized resources and tools for data retrieval and manipulation. Read and modify Odoo ERP records via MCP.

Maintenance / activity evidence

GitHub REST pushed_at 2026-10-09T08:54:38Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Reported action classes: create ERP records; update ERP records; delete ERP records. Complete write authority is not verified.
Odoo server URL, database and API key; module configuration
Sensitive access: ERP records, user credentials and business data

Read/create/update/delete per-model permissions; YOLO=true mode bypasses MCP security controls and is prohibited for production in upstream docs.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

401 repository stars

Stars observed Oct 9, 2026.

Repository total for ivnvxd/mcp-server-odoo.

All limitations / Review context

Has mcp-server-odoo changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

Read/create/update/delete per-model permissions; YOLO=true mode bypasses MCP security controls and is prohibited for production in upstream docs.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Odoo server URL, database and API key; module configuration
ERP records, user credentials and business data
Reviewed write actions: create ERP records; update ERP records; delete ERP records
Sensitive access: ERP records, user credentials and business data
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No exhaustive advisory or runtime review performed; never infer installation safety.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Original activity observations

GitHub REST pushed_at 2026-10-09T08:54:38Z

Technical identity

github.com/ivnvxd/mcp-server-odoo

Exact implementation source: https://github.com/ivnvxd/mcp-server-odoo ↗
Reviewed resource type: MCP Server
Repository identity: ivnvxd/mcp-server-odoo

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
ivnvxd/mcp-server-odoo
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

claude-desktop

Publisher instructions with a documented client setup path.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Configure the local server with the publisher `uvx mcp-server-odoo` command. Standard/production mode also requires the Odoo MCP module installed server-side; YOLO mode is documented for testing only.
mcp stdio launcher or diagnostic · Publisher instructions
uvx mcp-server-odoo
Configure / authenticate
MCP100 setup guide
Use uvx mcp-server-odoo in client stdio configuration. Production requires Odoo 16+ and the publisher Odoo MCP module; YOLO mode is development/testing only. Set ODOO_API_KEY and instance settings privately.
Advanced configuration · claude desktop json · MCP100 composed guide
claude desktop json · MCP100 composed guide
{ "mcpServers": { "odoo": { "args": [ "mcp-server-odoo" ], "command": "uvx", "env": { "ODOO_API_KEY": "YOUR_ODOO_API_KEY", "ODOO_DB": "YOUR_DATABASE", "ODOO_URL": "https://your-odoo-instance.com" } } } }
Check connection
Suggested check
Restart the MCP client and inspect Odoo tool discovery; call only read-only model listing in a test database, not a write operation.
Remove / uninstall / revoke
MCP100 setup guide
For Claude Code registration named odoo. For Desktop remove only mcpServers.odoo. Odoo server-side module is separately administered.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
claude mcp remove odoo

Official Documentation & Sources

What it does

Model Context Protocol (MCP) server that enables AI assistants to securely interact with Odoo ERP systems through standardized resources and tools for data retrieval and manipulation. Read and modify Odoo ERP records via MCP.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Read and modify Odoo ERP records via MCP

Representative uses

Find Odoo customers and products
Read ERP inventory and business records
Update allowed models with scoped permissions
Read and modify Odoo ERP records via MCP

Limitations

Read/create/update/delete per-model permissions; YOLO=true mode bypasses MCP security controls and is prohibited for production in upstream docs.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Odoo server URL, database and API key; module configuration
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: ERP records, user credentials and business data
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: Read/create/update/delete per-model permissions; YOLO=true mode bypasses MCP security controls and is prohibited for production in upstream docs.

Access scope and cautions

Write actions: Not verified create ERP records update ERP records delete ERP records
Sensitive access: ERP records, user credentials and business data
Risk level: high
Security notes: Read/create/update/delete per-model permissions; YOLO=true mode bypasses MCP security controls and is prohibited for production in upstream docs.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Find Odoo customers and products; Read ERP inventory and business records; Update allowed models with scoped permissions; Read and modify Odoo ERP records via MCP.

What setup and authentication are documented?

Recorded installation/entrypoint step: uvx mcp-server-odoo. Recorded environment-variable notes: ODOO_URL; ODOO_API_KEY; ODOO_DB. No configuration values are supplied here. Prerequisites: MCP-compatible client. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. Odoo YOLO=true bypasses standard module security controls and is development-only; YOLO=read is read-only testing mode. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Odoo server URL, database and API key; module configuration

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: create ERP records; update ERP records; delete ERP records. Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

ERP records, user credentials and business data Recorded sensitive-access context: ERP records, user credentials and business data.

What limitations and risks should I check before use?

Read/create/update/delete per-model permissions; YOLO=true mode bypasses MCP security controls and is prohibited for production in upstream docs. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. Repository pushed_at explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.