globus-mcp
Related Servers
Alternatives to globus-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI assistants and MCP clients to search Pyaterochka stores, browse categories, find products with filters for price, brand, and promotions, and retrieve product details, store hours, and promotion conditions through the exposed MCP tools.124MIT
- AlicenseNot gradedqualityFmaintenanceEnables interaction with the Rami Levy Online Grocery Store API, allowing users to perform product searches, add or remove items from their cart, and prepare for checkout, all while integrating with MCP-enabled LLMs.11MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage products, shopping carts, and orders in an online store through a well-defined MCP API.-
- AlicenseAqualityBmaintenanceEnables LLMs to read and manage a buyer's Ozon account data, including orders, purchase history, cart, favorites, product cards, and catalog search, using an authenticated session over the internal composer-api.425MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that turns Wildberries marketplace into a toolkit for LLM agents, enabling product search, detailed card inspection, price history, reviews, and cross-product comparison.-
- AlicenseAqualityAmaintenanceEnables searching WineLab's wine catalog and retrieving product details, filters, store locations, availability, and cart operations, with SMS-code login, from any MCP-compatible client.15MIT
TDQS
Scored across 22 tools
Most tools have clearly distinct resource+action purposes, especially the auth_, list_, search_, and cart_ groups. A few pairs, such as search_products vs. category_products and cart_add vs. cart_set_quantity, sit close together, but the descriptions are specific enough to resolve the ambiguity.
Tool names are readable and often grouped by prefixes like list_, auth_, search_, and cart_, but the convention is inconsistent. Bare nouns such as promotions and recommendations coexist with noun-ish names like product_details and checkout_info, and cart_set_quantity contrasts with set_purchase_method in word order.
22 tools cover a broad e-commerce workflow from authentication through catalog browsing, cart management, and checkout info, so the size is defensible. However, the count is on the heavy side of the calibration range, with some optional extras like auth_set_token, cms_page, and search_suggest that are not strictly required for the core flow.
Catalog, cart, and pre-checkout coverage are solid, but the checkout flow is a dead end: checkout_info explicitly does not place an order, and there is no order placement or order history tool. Auth is covered, but profile/address management is missing, leaving significant gaps for a shopping-focused MCP server.