Skip to main content
Glama

Related Servers

Alternatives to mcploy

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Enables Claude and other MCP clients to read and write a Loyverse point-of-sale account, covering catalogue items, inventory levels, loyalty customers, receipts and refunds through natural language. Includes a one-call sales summary that aggregates any date range into totals and ranked breakdowns by day, item, category, payment type, employee or store.
      41
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A local-first, read-only MCP server for the Loyverse POS API that lets AI assistants query receipts, items, employees, customers, stores, and sales analytics — built for secure local use with Personal Access Tokens.
      15
      11 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to interact with a point-of-sale public API through 32 MCP tools for managing bills, customers, items, orders, receipts, stock, suppliers, taxes, and webhooks over stdio and HTTP transports.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to fetch live exchange and cryptocurrency prices, persist key-value JSON records, and perform invoice, shipping, and inventory business logic through seven tools.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables an LLM agent to query a Shopify store's catalogue and stock via MCP, with tools for product search, product details, per-location inventory, and low-stock reports.
      4
      MIT

    TDQS

    A3.9/5.0

    Scored across 54 tools

    Disambiguation5/5

    Each tool targets a unique combination of action and resource (e.g., loyverse_create_category vs loyverse_list_category). No two tools overlap in purpose, making it easy for an agent to select the correct one.

    Naming Consistency5/5

    All tools follow the strict pattern 'loyverse_<action>_<resource>' in snake_case, providing a highly predictable and uniform naming scheme throughout.

    Tool Count4/5

    54 tools is a large number, but it corresponds to a wide range of resources (16 types) with full CRUD plus additional read-only endpoints. While on the higher end, the count is justified for the breadth of the POS system covered.

    Completeness4/5

    The tool set covers the core operations for most resources (create, read, update, delete where applicable). Some resources are read-only (e.g., merchant, shift) which is expected. Minor gaps like missing bulk operations or reports are acceptable for a basic API wrapper.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues