wb-mcp
Related Servers
Alternatives to wb-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to Wildberries and Ozon seller accounts for real-time access to sales, stocks, prices, finances, and reviews through official APIs.MIT
- AlicenseAqualityBmaintenanceConnects an AI assistant directly to Wildberries, Ozon, Yandex Market, and Avito seller accounts, letting it pull real sales, orders, stock, prices, finances, and reviews from each marketplace's API instead of guessing. It also requires confirmation before any price or stock changes are made.126MIT
- AlicenseAqualityCmaintenanceEnables AI agents to read and work with Wildberries, Ozon, and Yandex Market seller accounts through typed tools, multi-account support, unified data schemas, rate limiting, audit, and encrypted credential storage.1751 npmMIT
- AlicenseAqualityBmaintenanceWildberries seller API in your AI assistant: sales and stocks, product cards, prices and promotions, financial reports and reviews. 307 methods across all 17 Wildberries hosts live in a YAML catalog the server executes, the agent searches it in plain language, and every method carries an access class so writes and irreversible calls ask for confirmation.2561 PyPI5MIT
- AlicenseAqualityCmaintenanceEnables read-only analytics and product search for a Wildberries seller account, covering items, advertising, sales, stock, reviews, finances, and tariffs through MCP clients like ChatGPT or Cursor.12MIT
- AlicenseNot gradedqualityBmaintenanceLets AI agents read and query Wildberries, Ozon, and Yandex Market seller accounts through unified typed tools, with multi-account support, rate limiting, and encrypted credentials.51 npmMIT
TDQS
Scored across 8 tools
The core split between wb_get (read-only) and wb_call (mutating) is explicit and reinforced in both descriptions, and search/describe/sections serve clearly different discovery stages. The only fuzzy boundary is wb_request, which as a raw HTTP escape hatch can overlap with wb_get/wb_call for already-catalogued methods, though its 'new method not in catalog' framing mitigates this.
All tools uniformly use the wb_ prefix in lowercase snake_case, making the set instantly readable as one family. Minor deviation: most names are single verbs (search, describe, get, call, refresh) but wb_sections and wb_token_info are noun/noun+verb forms, so the pattern is not a pure verb_noun scheme.
Eight tools is tightly scoped for a catalog-and-invoke proxy: discovery (sections, search, describe), execution (get, call), auth diagnostics (token_info), and maintenance (refresh, request). Each tool has a distinct role and none feels redundant.
The search → describe → get/call workflow covers the full read and write lifecycle, with token diagnostics, catalog refresh, and a raw-request fallback for uncatalogued endpoints. Minor gaps: no way to enumerate all methods in a section (only counts), and no batch/pagination helper for high-volume reads.