groupon-mcp
Related Servers
Alternatives to groupon-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides MCP tools for discovering Groupon-style deals (search, get, compare) for customers, and additionally merchant intelligence tools (category insights, market gaps, price positioning) for logged-in merchants.-
- FlicenseAqualityCmaintenanceMCP server for searching and monitoring RedFlagDeals deals. Provides tools to search deals, get deal details, and set up monitors for new deals.6-
- AlicenseAqualityCmaintenanceMCP server for pelando.com.br, the Brazilian community deal board. It enables searching and browsing deals, retrieving deal details and comments, and assessing crowd quality verdicts.9BSD 2-Clause "Simplified"
- FlicenseAqualityBmaintenanceMCP server that acts as a shopping assistant, enabling product search, comparison, deal finding, and price history tracking via Hound web search.6-
- AlicenseBqualityFmaintenanceA Model Context Protocol server that aggregates and compares deals from multiple sources including Slickdeals, RapidAPI marketplace, and web scraping, enabling users to search, filter, and compare deals through a chat interface.67MIT
- FlicenseNot gradedqualityAmaintenanceMCP server for NYC Restaurant Week, enabling search and lookup of participating restaurants, date checks, and filter options.-
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: healthcheck, search, deal detail, categories, and cart operations. Even though 'purchase' might sound like buying, its description clearly defines it as adding to cart, preventing confusion.
All tools share the 'groupon_' prefix and mostly follow a verb_noun pattern (search_deals, get_deal, list_categories, view_cart, clear_cart). 'healthcheck' is a noun rather than a verb, and 'purchase' lacks an explicit object, making the naming slightly inconsistent but still predictable.
Seven tools is well-scoped for a Groupon deals and cart server. Each tool serves a clear, non-redundant purpose, and the count fits comfortably in the ideal 3-15 range.
The surface covers the core workflows: health check, searching/browsing deals, fetching deal details, viewing categories, adding to cart, viewing cart, and clearing cart. A notable gap is the lack of removing a single cart item or updating quantity, but the core lifecycle is otherwise covered.