woolies-mcp
Related Servers
Alternatives to woolies-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables 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.1216GPL 3.0
- AlicenseAqualityAmaintenanceA 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.141MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and comparing products from Woolworths and Coles supermarkets.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search Australian retailers and fill the user's own online shopping cart through tools for product search, adding items, setting quantities, and checking connection and usage status. Supports Woolworths today, with Coles, Amazon Australia, Kmart and BIG W planned.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables product search and authenticated grocery shopping-list management, including adding items, setting quantities, removing items, emptying the list, and reading purchase history.1MIT
- AlicenseNot gradedqualityBmaintenancePersonal 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 confirm100 npm14MIT
TDQS
Scored across 18 tools
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.
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.
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.
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.