migros-mcp
Related Servers
Alternatives to migros-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude to connect to a household's ICA account through BankID and access shopping lists, offers, bonus, stores, product lookup, catalogue search, purchase history, and Handla online prices. It also provides OAuth-based MCP connection, admin controls, audit logging, and optional list-writing tools.MIT
- AlicenseAqualityBmaintenanceEnables natural-language search of Swiss grocery products, price comparison, and weekly promotion lookup across retailers including Migros, Coop, Aldi, Denner, Lidl, Farmy, Volgshop, and Otto's.7MIT
- AlicenseAqualityDmaintenanceEnables shopping at Mercadona online grocery store via Claude, allowing catalog search, cart management, and order history retrieval while keeping payment control with the user.14MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to do grocery shopping through a logged-in drive session, including product search with labels, Nutri-Score and price per kilo, weekly promotions, usual products, purchase habit analysis, Open Food Facts quality checks, and cart quantity management.MIT
- FlicenseAqualityAmaintenanceA Model Context Protocol server for real-time Swiss grocery shopping that searches and compares products across 8 major Swiss retailers (Migros, Coop, Aldi, Denner, Lidl, Farmy, Volgshop, Otto’s), normalizes per-unit prices, surfaces promotions, computes optimal multi-store shopping plans, and works with any MCP-compatible client without API keys or accounts.7153 npm39-
- AlicenseAqualityCmaintenanceConnects Claude and other MCP clients to myGEKKO building controllers via the official Query API, enabling natural-language queries and control of smart-home devices. It is read-only by default, with write actions available only through explicit opt-in and safety policies.3MIT
TDQS
Scored across 105 tools
Despite the large surface, the tool set is organized by domain prefixes (cumulus_, checkout_, order_, shopping_list_, product_) and list-vs-single pairs (promotions/promotion_detail, cumulus_coupons/cumulus_coupon) are consistently delineated. A few boundaries remain fuzzy: search_products vs search_products_guest, checkout_context vs checkout_summary, and the promotions/weekend_promotions/promotion_detail/promotion_details cluster can still lead to misselection.
Names consistently use snake_case with a predictable prefix scheme (my_, cumulus_, shopping_list_, checkout_, order_, product_/category_/brand_/label_) and verb-first actions for mutations (add_, remove_, activate_, cancel_, place_, redeem_). Minor deviations exist: bare-noun read tools (receipts, inbox, favourites, promotions, teasers) and the tech-flavoured suffix in shopping_lists_firestore break the otherwise uniform pattern.
105 tools is far beyond the 3-15 sweet spot and even beyond the 25+ 'heavy' band; an agent must reason over a very large catalogue to pick correctly. The domain is genuinely broad (catalogue, loyalty, checkout, orders, content, recipes), but many adjacent read tools could have been consolidated (e.g. checkout_* group, promotion_* group) to keep the surface navigable.
Coverage is unusually deep: product discovery, categories, promotions, stores, fulfilment, full checkout and order lifecycle (place, authorize, cancel, invoice, payment slip), receipts, Cumulus loyalty, shopping lists, recipes and CMS content are all represented. Remaining gaps are minor: shopping-list lifecycle is partial (no create/rename/delete list or edit item quantity), and login is exposed only as a URL hint plus an external CLI rather than an in-server tool.