← ClaudeAtlas

lamoda-connectorlisted

Use this skill when the operator needs Lamoda fashion data — search or a product card with sizes. Trigger on "ламода", "lamoda", "кроссовки lamoda". Cards try anonymous GraphQL first, then the operator's Chrome when it is refused; search needs Chrome over CDP. Skip for non-Lamoda tasks.
Vladimir-Human/ru-marketplace-mcp · ★ 189 · DevOps & Infrastructure · score 88
Install: claude install-skill Vladimir-Human/ru-marketplace-mcp
# Lamoda Connector Two tiers by endpoint. The GraphQL product endpoint is tried over plain anonymous HTTPS first and, since 2026-10-12 when that started to meet the 307 loop too, through one in-page POST in the operator's Chrome (`tier_used: graphql_cdp`) — it enriches a SKU you already have with real prices, brand, sizes and availability. Everything that would find a SKU (search, catalog, HTML) sits behind the same 307 redirect loop as Ozon, so discovery runs in the operator's Chrome over CDP. ## When to use - Search Lamoda by text (CDP tier) - One product's price, old price, per-size availability (GraphQL: anonymous first, Chrome on refusal) ## Tools available - `lamoda_search(query)` — tiles from the rendered search page (CDP) - `lamoda_card(sku_or_url)` — GraphQL enrichment. SKU looks like MP002XM1RMM3; URLs carry it lowercased, the connector normalises. **Not an MCP tool:** `lamoda_selfcheck()` probes both tiers. It is CLI-only — `marketplace-mcp doctor` runs every connector's canary at once. ## Gotchas - Lamoda exposes NO ratings anywhere — `rating` is not in the GraphQL schema. No review tools exist here by design. - An empty search with a detected visible challenge returns `challenge_required`; it is not cached. Complete the interaction in the connected Chrome profile, then retry. Empty extraction without challenge evidence remains parser drift, not proof of "no results". - With `CHROME_CHALLENGE_HANDOFF_S` enabled, `handoff_expires_at` confirms a ret