Skip to main content
Glama
chrischall

groupon-mcp

by chrischall
README.md
# groupon-mcp

[![CI](https://github.com/chrischall/groupon-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/chrischall/groupon-mcp/actions/workflows/ci.yml)
[![npm](https://img.shields.io/npm/v/groupon-mcp)](https://www.npmjs.com/package/groupon-mcp)
[![license](https://img.shields.io/npm/l/groupon-mcp)](LICENSE)

MCP server for [Groupon](https://www.groupon.com) — search and browse local, goods, and travel deals from Claude via natural language.

> This project was developed and is maintained by AI. Use at your own discretion.

## Status

Early read-path MVP. Deal-read tools (search and browse over Groupon's public consumer endpoint) land in upcoming phases; this release establishes the server skeleton. No API key or account is required to read deals.

## Setup

Add the server to your `.mcp.json`:

```json
{
  "mcpServers": {
    "groupon": {
      "command": "npx",
      "args": ["-y", "groupon-mcp"]
    }
  }
}
```

## Development

```bash
npm install
npm run build   # tsc + esbuild bundle → dist/
npm test        # tsc typecheck + vitest
```

See [CLAUDE.md](CLAUDE.md) for architecture, conventions, and gotchas.

## License

MIT

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityNo data
ResponsivenessWithin a week