Skip to main content
Glama
adrian-baker

woolies-mcp

by adrian-baker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to woolies-mcp

No user-submitted related servers found.

    Related Servers

    • Woolworths MCP Server

      elijah-g
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Woolworths Australia's online shopping platform through browser automation and API integration. Supports product search, browsing specials, managing shopping cart, and accessing product details through natural language.
      12
      14
      GPL 3.0

    • trundler

      auckland-ai-collective
      A
      license
      A
      quality
      A
      maintenance
      A local MCP server for grocery shopping, enabling product search, specials, and browsing across NZ supermarkets, with cart and order history for Countdown/Woolworths via browser-assisted login.
      14
      1
      MIT

    • woolies-coles-mcp

      johnvouros
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and comparing products from Woolworths and Coles supermarkets.
      MIT

    • wegmans-mcp

      rtruxler
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables product search and authenticated grocery shopping-list management, including adding items, setting quantities, removing items, emptying the list, and reading purchase history.
      MIT

    • Basketeer

      tobyandrews1985
      A
      license
      Not graded
      quality
      B
      maintenance
      Personal UK Tesco grocery account over MCP: search, basket, slots, orders, and on-pack nutrition (search and rank by macros + micros). Catalogue + nutrition tools need no auth; destructive actions require a two-step confirm
      76 npm
      11
      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.1/5.0

    Scored across 18 tools

    Disambiguation3/5

    Most tools target a distinct resource, but sign_in and auth_status report nearly the same status, remove_from_cart duplicates set_cart_quantity(0), and search_products/search_products_batch are close variants. The descriptions clarify most boundaries, so selection is possible but not always obvious.

    Naming Consistency4/5

    Tool names mostly follow a verb_noun snake_case pattern (get_cart, search_products, set_location). Minor deviations like auth_status (no verb), browse_category (singular), and search_products_batch (suffix) prevent a perfect score, but the pattern is predictable overall.

    Tool Count3/5

    Eighteen tools is on the heavy side for a 3-15 tool well-scoped server, and several are redundant (auth_status vs sign_in, remove_from_cart vs set_cart_quantity, plus the batch search variant). The count is not chaotic, but it could be trimmed without losing functionality.

    Completeness4/5

    The surface covers catalogue browsing, product detail, search, specials, location, cart management, and order/purchase history. The main gap is the absence of checkout/order placement, but for a shopping-assistant domain the core workflows are present and workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources