yt-mcp-server-odoo

Provides an MCP server/client in Python that lets AI assistants search, read, create, update, delete, and bulk-manage records in an Odoo ERP instance via MCP tools mapped to Odoo model operations. Configuration is done through environment variables, including an Odoo API key for authorization, and supports MCP stdio or streamable-http transport modes.

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ Repo ↗ Infrastructure mcp odoo erp ai-assistants tooling python
⚙ Agent Friendliness
56
/ 100
Can an agent use this?
🔒 Security
60
/ 100
Is it safe for agents?
⚡ Reliability
20
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
70
Documentation
65
Error Messages
0
Auth Simplicity
65
Rate Limits
10

🔒 Security

TLS Enforcement
80
Auth Strength
70
Scope Granularity
35
Dep. Hygiene
60
Secret Handling
55

Security is dependent on Odoo API key/user permissions (good principle of least privilege), but the README does not describe secret-handling practices (e.g., whether secrets are logged), authorization granularity beyond model permissions, TLS requirements/enforcement details, or rate limiting. YOLO mode is explicitly risky for tool/model access.

⚡ Reliability

Uptime/SLA
0
Version Stability
25
Breaking Changes
20
Error Recovery
35
AF Security Reliability

Best When

You want an AI assistant to interact with Odoo through explicit MCP tools, and you can provision an Odoo user/API key with appropriate model permissions.

Avoid When

You cannot restrict the MCP tool access or Odoo permissions, or you rely on this service without understanding the implications of create/update/delete (including bulk operations).

Use Cases

  • AI-assisted querying of Odoo records (e.g., find customers, invoices, products)
  • AI-assisted CRUD operations in Odoo with model-aware tool calls
  • Automating common ERP workflows using pre-defined prompt templates
  • Bulk creation/updating of records driven by natural language

Not For

  • Untrusted/public environments without strong secrets handling
  • Use cases requiring fine-grained audit logging or strict data minimization guarantees (not documented here)
  • Environments that cannot safely permit create/update/delete actions from an agent

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: ODOO_API_KEY (Odoo API key used by the MCP server) ODOO_USER + ODOO_PASSWORD (alternative credentials)
OAuth: No Scopes: No

Authentication is via an Odoo API key (preferred per README) or optionally username/password. The README emphasizes that Odoo user permissions govern access to models/operations; explicit OAuth scopes are not described.

Pricing

Free tier: No
Requires CC: No

No pricing information is provided; appears to be an open-source Python package.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • YOLO mode can bypass MCP model restrictions; enabling 'true' is dangerous even if Odoo permissions still apply.
  • Create/update/delete and bulk operations increase the risk of unintended data modification by an agent if prompts are vague.
  • Model visibility depends on MCP-enabled models configuration and/or YOLO mode behavior.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for yt-mcp-server-odoo.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered