odoo-safe-mcp
Related Servers
Alternatives to odoo-safe-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to interact with an Odoo ERP through tool calls that are allowlist-policy-checked, risk-scored and throttled before touching the ERP, covering record reads, writes, deletes and method execution. Every request and decision is recorded to a hash-chained, tamper-evident audit log with optional HMAC keys and anchor exports.19MIT
- AlicenseAqualityBmaintenanceEnables AI agents to interact with Odoo ERP as the authenticated user, with tools for discovery, planning, and mutations bounded by user permissions.3665 npm2Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with Odoo ERP systems through natural language to search records, create entries, update data, and manage business operations. Supports secure authentication and configurable access controls for production environments.Mozilla Public 2.0
- AlicenseNot gradedqualityCmaintenancePlaces an MCP server in front of Odoo so AI agents can read live ERP data — stock by warehouse, reorder suggestions, invoices, sales, purchase and manufacturing orders — and draft proposed writes such as purchase orders, stock transfers, manufacturing orders and vendor bills. Every change is queued for human approval before it is written to the ERP, with per-client scopes, warehouse restrictions, rate limits and a full audit log of each call and decision.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants like Claude, ChatGPT, and Copilot to connect to Odoo ERP, providing tools to search, read, create, and update any Odoo model such as partners, sales orders, invoices, and products.11 npmAGPL 3.0
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Odoo ERP via the external API. It supports listing models, describing schemas, searching, aggregating, creating, updating, deleting records, and invoking business methods, with a configurable permission matrix for safety.-
TDQS
Scored across 8 tools
Dedicated read/search/count/aggregate and metadata tools are clearly separated, and execute_kw is framed as the generic write/ORM path. Some overlap remains because execute_kw can also perform reads and approval_status both checks and may execute a pending write, but the descriptions make intended use fairly clear.
All names use the odoo_ prefix and snake_case, with predictable verb/resource ordering in describe_model, list_models, approval_status, and execute_kw. A few names are verb-only (search, read, count, aggregate) rather than full verb_noun, but the set remains readable and consistent.
Eight tools is well within the appropriate range for a general-purpose Odoo server. The split between read helpers, metadata discovery, approval handling, and generic execution is purposeful and each tool earns its place.
The surface covers discovery, querying, aggregation, and writes through execute_kw, including an approval workflow for critical operations. There are minor gaps such as no explicit pending-approval listing and CRUD being indirect via execute_kw, but the core lifecycle is reachable.