Skip to main content
Glama
samuelseidel

alza-mcp

by samuelseidel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to alza-mcp

No user-submitted related servers found.

    Related Servers

    • Tokopedia MCP Server

      oshimayoan
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search for products and manage order history on Tokopedia using the Model Context Protocol. It supports advanced filtering, sorting discovery, and authenticated session management via a dual MCP and web interface.
      1 npm
      1
      MIT

    • Rohlik MCP

      tomaspavlin
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Rohlik Group's online grocery delivery services across multiple countries, including product search, cart management, and account info.
      27 npm
      120
      MIT

    • Rohlik MCP Server

      kolarova-ops
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Rohlik Group's online grocery delivery services across multiple European countries, supporting product search, shopping cart management, order history analysis, and personalized meal suggestions based on purchase patterns.
      27 npm
      3
      MIT

    • Kroger MCP Server

      EricLott
      A
      license
      Not graded
      quality
      D
      maintenance
      Allows Large Language Models to interact with Kroger's grocery services, enabling product search, store lookup, and cart management through the Model Context Protocol.
      3
      MIT
    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

    A4/5.0

    Scored across 41 tools

    Disambiguation3/5

    Many tools come in close pairs (cart/web_cart, add_to_cart/web_add_to_cart, place_order/web_place_order, pay_after_order/web_pay_after_order) and the descriptions work hard to disambiguate them, but an agent can still easily pick the wrong one — especially since the mobile checkout path is documented as broken while the web one works. The generic mobile_read escape hatch also overlaps with several typed tools. On the other hand, the intent of most tools is clear from the descriptions.

    Naming Consistency3/5

    There is a loose verb_noun pattern (search_products, get_product, list_categories) but many read tools are bare nouns (cart, profile, order, contacts) and the web_ prefix is applied inconsistently (web_cart noun vs web_place_order verb). The pair after_order_payments vs pay_after_order and web_pay_after_order breaks the expected verb-first ordering. Mixed but still readable.

    Tool Count2/5

    41 tools is a heavy surface for an e-commerce server, even a broad one. Several tools exist as workarounds or generic escape hatches (mobile_read, prepare_mutation, mutate_list) and there are duplicated mobile/web checkout paths that could have been consolidated. This exceeds the comfortable range and will burden an agent with selection overhead.

    Completeness4/5

    The domain is covered extensively: discovery, product details, reviews, categories, pickup points, auth, cart, checkout, payments, orders, profile, addresses, registration, subscriptions, complaints, and chat. Notable gaps remain — notably no cart-removal tool (explicitly acknowledged) and no order cancellation or return flow — but agents can accomplish the main shopping journey.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources