boogh-mcp
# boogh
Snapp ride + SnappFood CLI. Stdlib only.
Reads old tokens from `~/.config/snapppp/tokens.json` on first run,
writes to `~/.config/boogh/tokens.json`.
```bash
uv sync
uv run boogh food cities
uv run boogh food vendors
uv run boogh food menu 3kv8mn
uv run boogh geo "میدان ونک"
uv run boogh ride price --origin "میدان ونک" --dest "تجریش"
uv run boogh ride profile
uv run boogh ride place
uv run boogh ride history --limit 5
```
Reads default to home location, no flags needed.
`--origin`/`--dest` take `lat,lng`, a saved name (`Home`, `دفتر`), or Persian text.
Writes never fire without `--confirm`. Default prints dry-run.
## MCP
Stdio server, same ops, no extra deps:
```bash
uv run boogh-mcp
```
Point any MCP client at it (command `uv`, args `["run", "--project", "/path/to/boogh", "boogh-mcp"]`).
Every op is a tool (`food_vendors`, `ride_price`, `ride_login_send`, ...),
generated from the same registry, so CLI and MCP never drift.
Writes need `"confirm": true` in args, otherwise they return dry-run.
TDQS
Scored across 55 tools
Domain prefixes (food_ vs ride_) help separate the two services, but several tools have overlapping purposes: geo vs food_place/food_reverse for geocoding, ride_status vs ride_track for active ride state, and ride_price vs ride_options_quote vs ride_flexi for quotes. Descriptions are terse and do not fully clarify the boundaries.
Most tools use snake_case with a domain prefix (food_* or ride_*), but the verb/noun pattern is mixed: some tools are noun-only (ride_status, food_menu) while others are verb_noun (ride_cancel, food_basket_create). Additionally, one tool (geo) lacks a domain prefix, breaking the pattern.
With 55 tools, the set is extremely large and exceeds the 50+ threshold that indicates an extreme mismatch for an MCP server. Even accounting for two domains (ride and food), the volume is overwhelming and likely to burden an agent's selection process.
The surface covers most core workflows for both ride-hailing (login, profile, places, quotes, request, cancel, track, history, payments, carpool) and food ordering (login, profile, vendors, menus, baskets, orders, reviews). Minor gaps exist, such as no food order cancellation or past order history tool, but these are workable.