mcp-supermercados-cl
Related Servers
Alternatives to mcp-supermercados-cl
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to search products, compare prices, and find the best deals across multiple supermarkets in Argentina through Superprecio's price comparison API. Transforms Claude into an expert shopping assistant for Latin American grocery shopping.1514 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and comparing products from Woolworths and Coles supermarkets.MIT
- FlicenseNot gradedqualityBmaintenanceEnables users to compare and get recommendations across multiple supermarket products, combining curated specifications with realtime price and review lookups.-
- FlicenseBqualityDmaintenanceEnables cross-store price comparison and recipe-driven cart automation for Israeli grocery stores Shufersal and Tiv Taam, with an extensible architecture for additional stores.14-
- FlicenseNot gradedqualityDmaintenanceProvides grocery price and nutritional information search capabilities, allowing AI agents to search for food products, compare prices, and analyze nutritional content across different grocery stores.1-
- FlicenseAqualityDmaintenanceEnables AI assistants to track global food prices, search products by barcode or name, and compare costs across 27 countries. It provides tools for real-time price scraping and data aggregation from major international supermarket chains.84-
TDQS
Scored across 14 tools
Most tools target distinct resources/actions, and rich descriptions separate search, offers, cart, lists, and cross-store comparisons. Some pairs overlap conceptually (get_offers vs find_opportunities, build_list vs suggest_swaps, compare_stores vs build_cheapest_basket), but the descriptions provide enough cues to avoid serious misselection.
Names overwhelmingly follow a clear verb_object snake_case pattern (get_saved_lists, build_list, search_products, compare_stores). The main deviation is adapter_status, which is a noun phrase rather than an imperative verb and would be more consistent as get_adapter_status.
At 14 tools, the count is within the ideal 3-15 range and matches the broad scope of a multi-chain supermarket assistant. Each tool covers a distinct workflow step, from product discovery to cart management and store comparison, so none feels redundant.
The surface covers the core shopping lifecycle well: search, product details, offers, list building, frequent products, cart reads/updates, and cross-store cost comparison. Minor gaps remain, like no saved-list mutation and no explicit cart item removal, but agents can work around these without dead-ending.