logimu-shopping-mcp
# Logimu Shopping MCP
**Give Claude, ChatGPT, and any MCP client real shopping data.**
AI assistants are great at comparing products — and terrible at knowing today's price, what's actually in stock, and which "bestseller" is a relabeled generic. This MCP connector fixes that: your assistant gets **observed Amazon (US, UK, DE, CA, AU, FR, IT, ES, JP, MX, BR) and Walmart US data** — current prices, live stock, real ratings, price/BSR history, and ranked product shortlists — from a continuously refreshed warehouse of 17M+ tracked products.
**Free, no signup: 30 queries per day.**
```
https://api.logimu.com/mcp
```
## Quick start
| Client | How |
|---|---|
| **Claude** (claude.ai / desktop) | Settings → Connectors → Add custom connector → paste the URL above. No key needed. |
| **Claude Code** | `claude mcp add --transport http logimu https://api.logimu.com/mcp` |
| **ChatGPT** (developer mode), Cursor, VS Code, anything MCP | Add the same URL as a remote (Streamable HTTP) server. |
Then ask things like:
- *"Find me the best coffee maker under $80"* → ranked shortlists grouped by category or price tier
- *"Is ASIN B0BDHQSZCV a good buy right now?"* → price, stock, buy-box seller, 30-day price/stock changes, brand stats
- *"Well-rated dehumidifiers under $150 with 1,000+ reviews"* → structured warehouse filtering
## Tools
| Tool | Use when | Returns | Lane |
|---|---|---|---|
| `shopping` | "best X", "find me Y under $Z" — you want a shortlist | Ranked, grouped products (category or Budget/Mid/Premium tiers) with real ratings, prices, stock, `observed_at` stamps + brand facets, in ~100ms | Free: 1 of 30 daily |
| `product` | You have a specific ASIN/item — "good buy?", "price history?", "who sells this?" | Current snapshot + intelligence blocks: 30-day price/stock change events, all-seller offer table, brand stats; full price, rank and buy-box histories with a key (included in the record), or `history_only` for the series alone (0.05 credit) | Free: 1 of 30 daily |
| `search` | Filtered structured lists — price/rating/review/BSR/FBA filters, sorting | Up to 25 rows on the free lane, across all 11 Amazon marketplaces plus Walmart US | Free: 1 of 30 daily |
| `serp` | The live Amazon search-results page for a query, right now | Organic grid, sponsored and video blocks, refinements, pagination — a real fetch, seconds | API key: 1 credit per page fetched |
| `bestsellers` | What sells best in a category right now; Amazon's best-seller category tree | Up to 100 products in Amazon's rank order, the category's breadcrumb name and its subcategories; a root URL or a country alone returns the top-level categories. A real fetch (seconds), cached up to 30 min | API key: 1 credit per page of 50 (top 100 = 2), root list free |
| `offers` | Who sells a product right now, at what price; the cheapest new or used offer; the buy-box winner this minute | Every offer on Amazon's offers page (every page): seller and seller id, price, shipping, condition, buy box, FBA / FBM / Amazon, Prime, delivery promise and the seller's feedback, by ASIN or barcode. A real fetch (seconds); a no-offers answer is confirmed by a second, independent fetch | API key: 0.5 credit when an offer is listed; no offers, a miss or a failed fetch free |
| `seller` | A seller id — rating and feedback history, the storefront, the brands it was observed winning the buy box on, connected sellers | Stored profile (0.5) or live (1), +0.5 history; storefront pages 1 each; `brands` / `network` blocks +1 | Paid plan |
| `brand` | Who sells a brand, how contested / Amazon-dominated / FBA-heavy it is, its seller map | Brand dossier from observed buy-box data (1), +0.5 history, +1 per sellers page, +1 for the network of brands sharing sellers | Paid plan |
| `category` | How big / competitive / Amazon-dominated a category is, which brands lead it | Category landscape by id (1, +0.5 history); the name lookup is free | Paid plan |
| `market_lists` | Discover rather than look up — brands gaining or losing sellers, the biggest operators, categories ranked | 25 rows per page, 1 credit per page | Paid plan |
| `keywords` | Amazon's own autocomplete suggestion lists for a seed (positions within each list, first/last observed, marketplaces observed in, related vocabulary), `history` = each list's observation record, `compare` = the seed across marketplaces | 1 credit per lookup or compare, +0.5 with history | Paid plan |
The paid-plan tools (`seller`, `brand`, `category`, `market_lists`, `keywords`) appear in `tools/list` only for keys on a paid plan; the stub lists the whole catalog so directories can see it. Every derived figure is an observed count or share from Logimu's own data — never an estimate — and "observed since" is the data horizon, not a founding date. Keyword answers are Amazon's own suggestion ranking as observed — positions within one list, never volume figures and never a product-ranking map.
Full REST API reference (same engine, same data): [api.logimu.com/docs](https://api.logimu.com/docs)
## Free lane and paid plans, honestly stated
| | Free (no signup) | Paid plan (API key) |
|---|---|---|
| Queries | 30 / day | Credit-metered — subscriptions from $19/month, one-time credit packs, unconditional 14-day money-back |
| Data | Warehouse `shopping` / `product` / `search`, cached (fresh, timestamped) | + `mode=live` on-demand fetches, `serp`, `bestsellers`, `offers`, seller profiles, brand / category intelligence and market lists, batch jobs on the REST API |
| Signup | None | [api.logimu.com](https://api.logimu.com) |
- Every record carries an `observed_at` timestamp — data is **observed** from our warehouse, not a live retailer feed.
- We have **no affiliate or seller relationship** with anything the tools return. Nothing is ranked because someone paid for it.
- Failed or empty requests are never billed, on any tier.
## What's in this repo
The live server is **hosted** — this repo carries the tool catalog, an introspection-only stdio stub (`logimu-mcp-stub`) so directory build harnesses can enumerate the tools without credentials, and the listing metadata. `tools/call` on the stub returns a pointer to the hosted endpoint.
```bash
pip install .
logimu-mcp-stub # stdio MCP: initialize / tools/list work; tools/call points to the hosted server
```
## Links
- Product page: [logimu.com/shopping-mcp](https://www.logimu.com/shopping-mcp/)
- API console & plans: [api.logimu.com](https://api.logimu.com)
- Docs: [api.logimu.com/docs](https://api.logimu.com/docs)
- Privacy: [logimu.com/privacy-policy](https://www.logimu.com/privacy-policy/) · Terms: [logimu.com/terms](https://www.logimu.com/terms/) · Refunds: [logimu.com/refund-policy](https://www.logimu.com/refund-policy/)
- Support: support@logimu.com
---
© 2026 Logimu · A service of CP Development doo · Not affiliated with Amazon or Walmart.
TDQS
Scored across 3 tools
Each tool serves a distinct purpose: product for detailed history of a specific item, shopping for ranked discovery from keywords, and search for filtered queries. Descriptions explicitly state when not to use each, eliminating ambiguity.
Tool names are single-word nouns (product, shopping, search) with a consistent style, though they mix parts of speech (noun, gerund, noun/verb). The pattern is clear and predictable, with minor variation.
Three tools are well-scoped for a shopping assistant: product depth, discovery, and filtered search. No unnecessary tools, and the count is appropriate for the domain.
The tool set covers core shopping workflows: discovery, search, and detailed product history. Minor gaps (e.g., no textual review access) exist but don't hinder typical agent tasks.