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: 5 shopping searches per day. Every other tool needs a Logimu plan (from $19/month).**
```
https://api.logimu.com/mcp
```
## Quick start
| Client | How |
|---|---|
| **Claude** (claude.ai / desktop / mobile) | Settings → Connectors → Add custom connector → paste the URL above. **Authentication:** *Sign in now* if you have a Logimu plan (every tool, metered on your plan; OAuth, the connector never sees your key), or keep the pre-selected *No sign-in* for the free `shopping` tool only. **OAuth client:** keep *Use Claude's published identity*. Claude can't change this choice later: remove the connector and add it again. |
| **Claude Code** | `claude mcp add --transport http logimu https://api.logimu.com/mcp`, then `/mcp` to sign in when a paid tool asks, or `--header "Authorization: Bearer sk_live_…"` to pass the key directly |
| **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, without `detail`; plan: 2 credits, 5 with `detail` |
| `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) | Paid plan: 0.5 credit from cache, 1 live |
| `search` | Filtered structured lists — price/rating/review/BSR/FBA filters, sorting | Up to 100 rows, across all 11 Amazon marketplaces plus Walmart US | Paid plan: 1 credit per 25 rows |
| `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 |
| `deals` | What is on sale on Amazon right now: today's deals or lightning deals in a department, deals above a discount or under a price, coupon deals, deals ending today | Amazon's Today's Deals page, filtered as Amazon filters it (department, deal collection, % off, price, Prime Exclusive, rating, brand): deal and list price, % off, deal type and state, % claimed, the countdown end, coupon; plus the departments, collections and facets to filter by next and `filter_check` (did Amazon apply each filter). A real fetch (seconds a page), cached up to 15 min | API key: 1 credit per page fetched (up to 120 deals a page); an empty page 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 |
| `keyword_rankings` | Page 1 of Amazon US search as last observed (about weekly) for head search terms: the organic order with product facts and each product's latest buy box, the sponsored units in the page HTML, the Overall Pick holder, who holds the page by brand and seller, and what changed since the previous observation; `history` = the weekly observations. Dated observations, never volume figures | 1 credit a keyword, +0.5 with history | Paid plan |
| `product_keywords` | Reverse ASIN on Amazon US: every observed keyword a product shows up for on page 1, with its rank; `asins` (up to 10) compares it with competitors and `gaps` keeps the keywords where they appear and it does not; `history` = its rank over time. Head search terms and page 1 only | 1 credit per 25 keywords per ASIN, +0.5 with history | Paid plan |
The paid-plan tools (`product`, `search`, `seller`, `brand`, `category`, `market_lists`, `keywords`, `keyword_rankings`, `product_keywords`, `track_product`, `list_tracked`) 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; the observed page-1 positions of products are `keyword_rankings` and `product_keywords`.
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 | 5 `shopping` searches / day | Credit-metered — subscriptions from $19/month, one-time credit packs, unconditional 14-day money-back |
| Data | `shopping`: ranked shortlists from the warehouse (fresh, timestamped), without `detail` | + `product` records with history, `search`, `shopping` `detail`, `mode=live` on-demand fetches, `serp`, `bestsellers`, `offers`, `deals`, 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 18 tools
The descriptions work hard to fence tools off with explicit USE WHEN / DON'T USE clauses, but the surface still contains three overlapping clusters: discovery (shopping vs search vs serp, plus bestsellers), keyword analysis (keywords vs keyword_rankings vs product_keywords), and current offers/history (offers vs product, which also returns an all-seller offer table). An agent with those clusters plus a live-vs-cached distinction to track will occasionally misselect, especially shopping vs search vs serp, whose boundaries are described rather than structural.
Names mix bare singular nouns (product, shopping, search, seller, brand, category, offers, deals, account, batch) with verb_noun forms (track_product, list_tracked) and noun_noun forms (keyword_rankings, product_keywords, market_lists). Nothing is chaotic and all names are readable, but there is no predictable pattern an agent can rely on and several nouns are vague in isolation (product, shopping, search).
18 tools is at the heavy end but each maps to a real, distinct Amazon/Walmart intelligence surface (product dossier, discovery, search, SERP, offers, deals, bestsellers, seller, brand, category, lists, keywords x3, tracking x2, batch, account). The count is justified by the breadth rather than padded, though the tiermarketplace/plan-gating means many tools stay invisible to free users.
Coverage is broad and lifecycle-complete in most directions: historical product dossiers, current offers, live pages, catalog search, discovery, brand/category/seller intelligence, keyword and reverse-ASIN, plus tracking and batch orchestration. Minor gaps: no standalone review retrieval (only embedded in product's detail path), no way to query historical price drops across a set, and alert management is only partially exposed via track_product/list_tracked.