Sklarstad Storefront MCP
Related Servers
Alternatives to Sklarstad Storefront MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to search enterprise Auto-ID products and exact SKUs, read live stock and current pricing, and explore variants, accessories, consumables and support relationships through a public read-only endpoint. It also surfaces manuals, firmware, drivers and other verified technical resources from the vendor's support center.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to browse product catalogs, search products with filters, and initiate checkouts, generating order summaries and checkout URLs.-

Toolzy MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, view details, and check availability of tool rental listings from Toolzy's peer-to-peer marketplace.MIT- AlicenseAqualityBmaintenanceEnables AI assistants to search, compare, and discover ecommerce tools through a free, read-only directory, including finding alternatives, listing tasks and platforms, and retrieving tool details.6MIT
- AlicenseAqualityCmaintenanceEnables an AI agent to look up products by exact ID or browse them by collection, and to check an order's status with each line item resolved to its full product details in a single call. Returns structured JSON with pricing, stock, and shipping data, and surfaces graceful error results for unknown IDs.2MIT

aisles-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to search products and check whether specific items are in stock at nearby physical stores in covered US cities, returning store prices and last-checked times through read-only tools.830 npmMIT
TDQS
Scored across 3 tools
Each tool has a clear, non-overlapping purpose: list_products provides an overview, get_product gives full details for a single product, and get_checkout_url retrieves the purchase link for a specific tier. An agent can easily distinguish which tool to call based on the information needed.
All tool names follow a consistent verb_noun pattern (list_products, get_product, get_checkout_url). The naming is predictable and aligns with standard conventions, making it easy to infer functionality.
Three tools is well-scoped for a storefront MCP. Each tool serves a distinct, necessary function (browse, inspect, purchase) without redundancy or bloat. The count feels appropriate for the domain.
The tool surface covers the complete customer-facing lifecycle: listing products, retrieving full details, and obtaining checkout URLs. There are no obvious gaps for the stated purpose, and the inclusion of pricing tiers and availability in get_product avoids dead ends.