Skip to main content
Glama
JamiTheS

odoo-mcp

by JamiTheS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to odoo-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-server-odoo

      altinkaya-opensource
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to fully interact with Odoo ERP instances over XML-RPC, supporting read and write operations on any model without requiring Odoo module installation.
      4
      AGPL 3.0

    • MCP Odoo Server

      malvernbright
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Odoo databases via XML-RPC and JSON-RPC for performing CRUD operations and managing modules. It supports advanced features like domain-based searching, field metadata inspection, and administrative task execution.
      6 npm
      MIT

    • MCP Server for Odoo

      otomatercom-cloud
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely access and perform CRUD operations on Odoo data through natural language, with granular permissions and dual REST/XML-RPC support.
      -

    • Odoo MCP Server

      sebastianPhoenix
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Odoo ERP systems through XML-RPC communication. Provides access to Odoo models, records, methods, and data structures for comprehensive ERP integration.
      2
      MIT

    • Odoo MCP Server

      keysersoft
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      7 npm
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: search, read, count, aggregate, name_find, create, write, unlink, upsert, etc. are all separate operations. The main ambiguity is odoo_execute, which is a generic method caller that could overlap with many others, and odoo_write vs odoo_update_where, though the descriptions clarify the difference (by IDs vs by domain).

    Naming Consistency4/5

    All tools share the odoo_ prefix, which creates a strong brand, but the second part mixes nouns (models, fields, status), verbs (search, read, create), and verb-noun compounds (enable_write, update_where, name_find, get_attachment). Some names like odoo_name_find are oddly ordered, but overall the pattern is predictable and readable.

    Tool Count3/5

    With 32 tools, the server is on the heavier side, but the scope is broad: it covers ORM operations, imports/exports, attachments, journaling, demo features, and dashboards. Each tool appears to serve a distinct function, so the count feels justifiable for an Odoo integration, even if it exceeds the typical well-scoped range.

    Completeness5/5

    The tool surface is remarkably complete: it includes connection management, model/field introspection, search/read/count/aggregate, create/write/unlink/upsert, bulk updates, file import/export, attachment retrieval, a journaling system, demo preparation, and dashboard creation/inspection. There are no obvious dead ends for common Odoo workflows, and odoo_execute covers any missing long-tail operations.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources