Odoo MCP Server
Related Servers
Alternatives to Odoo MCP Server
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityBmaintenanceConnects Claude Desktop or Claude Code to a company's Odoo instance with a one-click extension or installer, automatically negotiating the right API (web session, JSON-2, or JSON-RPC) for any Odoo version. Exposes tools that let Claude search, read, count, group, create, update, delete, and link Odoo records as the logged-in user, with an optional read-only mode.MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to control any Odoo database via XML-RPC, with features for reading, writing, importing/exporting data, and generating intervention reports.32MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to securely access and perform CRUD operations on Odoo data through natural language, with granular permissions and dual REST/XML-RPC support.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to securely access and interact with Odoo data through natural language, supporting CRUD operations, attachments, and role-based permissions.-
- AlicenseBqualityCmaintenanceConnects MCP clients like Claude to your Odoo ERP, enabling natural language queries, reports, and optional data modifications.9MIT
TDQS
Scored across 6 tools
Each tool targets a distinct resource or view: leads, partners, sales orders, unpaid invoices, pipeline aggregate, and lead creation. The only mild overlap is list_leads versus pipeline_summary, but one returns records and the other aggregates by stage, so the descriptions make the boundary clear.
Five of six names follow a clean verb_noun pattern (list_leads, search_partners, get_sales_orders, get_unpaid_invoices, create_lead). pipeline_summary is a noun-only outlier, but it is still readable and unambiguous.
Six tools is well-scoped for a CRM/sales assistant, with each tool covering a distinct question type (pipeline, contacts, orders, receivables, creation). No redundant or filler tools.
The surface is read-heavy with a single write path (create_lead): there is no update/advance lead, no close/won-lost action, no quotation or sales-order creation, and no invoice detail or payment marking. Core read workflows are covered, but lifecycle coverage is notably partial for a sales CRM.