Skip to main content
Glama
Lightspeed X-Series MCP

Lightspeed X-Series MCP

by davidboulay

Related Servers

Alternatives to Lightspeed X-Series MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to Lightspeed X retail data (sales, inventory, products, customers) with aggregated reporting on revenue, COGS, profit, and other metrics for MCP clients like Claude.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language, read-only access to your Cakto payment gateway data, including orders, revenue analytics, subscriptions, churn, customers, and products.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude and other MCP clients to query live online-store product, order, sales, stock, and customer data in plain English, with secure read-only defaults, masked customer information, capped results, and audit logging.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables e-commerce clients to query their own analytics data in plain English with strict tenant isolation enforced by the database.
      MIT

    TDQS

    C2.9/5.0

    Scored across 35 tools

    Disambiguation3/5

    Most tools target a distinct resource/action, but api_get is a catch-all GET that overlaps with every specific read tool. Product and inventory tools (search_products, list_products, get_product, get_inventory, list_inventory_levels) also require careful selection, though descriptions help.

    Naming Consistency4/5

    The set is mostly consistent snake_case verb_noun naming (list_*, get_*, search_*). Minor deviations like api_get, sales_summary, and find_gift_card keep it from being perfectly uniform.

    Tool Count2/5

    35 tools is heavy for an MCP surface, even for a broad retail API. Many read/list/get variants could be consolidated or handled through fewer well-scoped tools plus the generic api_get.

    Completeness3/5

    Read coverage is broad across products, inventory, sales, customers, gift cards, and promotions, but the entire write/update/delete side is absent because every tool is a GET-style read. This is a notable gap for full lifecycle coverage.