Skip to main content
Glama
huzaifafarooqusa-spec

ecom-ops-mcp

by huzaifafarooqusa-spec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ecom-ops-mcp

No user-submitted related servers found.

    Related Servers

    • shopify-store-mcp

      xmqywx
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage Shopify stores via natural language, with tools for products, orders, inventory, customers, and analytics.
      5 npm
      MIT

    • Shopify Agentic MCP Gateway

      kuro-tomo
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to autonomously browse inventory, negotiate terms, manage carts, and execute secure payments on Shopify stores using standardized protocols. It provides a bridge for LLMs to handle the entire commerce lifecycle from discovery to order tracking through a verifiable mandate chain.
      5
      2
      MIT

    • Odoo AI Telegram MCP

      prashantk8ursrvc-ux
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes 104 Odoo tools across CRM, Sales, Inventory, Accounting, and Helpdesk, enabling natural-language control of an Odoo instance via a Telegram assistant with user-level authentication and multi-step orchestration.
      -

    • MCP Server for Odoo

      elevateinformatics
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Odoo ERP systems through natural language, allowing users to search, create, update, and manage business records like customers, products, and invoices across any Odoo instance.
      1
      Mozilla Public 2.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.1/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly separated by system prefix and resource, but odoo_search_read is a generic fallback that overlaps with odoo_get_stock_levelanding fulfill_shopify_order duplicates the multi-tool workflow, creating some selection ambiguity for agents.

    Naming Consistency3/5

    Naming follows a mostly verb_noun pattern with system prefixes, but conventions differ: shopify_get_orders vs odoo_search_read, export_report_to_excel lacks a system prefix, and fulfill_shopify_order inverts the prefix order. This mixed style is readable but not fully consistent.

    Tool Count5/5

    Eleven tools cover three external systems plus reporting and a composite workflow without feeling bloated. Each tool has a clear niche, and the count aligns well with the server's multi-system e-commerce operations scope.

    Completeness4/5

    The core order-to-fulfillment lifecycle is covered: fetch Shopify orders, create Odoo sale orders, manage Asana tasks, and export data. Minor gaps exist—no Shopify order updates, no single Asana task detail, and no Odoo sale order modification—but the generic odoo_search_read and composite fulfill tool mitigate most dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources