Skip to main content
Glama
sklarstad

Sklarstad Storefront MCP

by sklarstad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Sklarstad Storefront MCP

No user-submitted related servers found.

    Related Servers

    • ro.autoid/autoid-support

      AutoID-Alex
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      -
    • Toolzy MCP Server by Toolzy-2

      Toolzy MCP Serverofficial

      Toolzy-2
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search, view details, and check availability of tool rental listings from Toolzy's peer-to-peer marketplace.
      MIT

    • By Adunni MCP Server

      FopeA6
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      2
      MIT

    • aus-cart-mcp

      TheDancingDeveloper-org
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search Australian retailers and fill the user's own online shopping cart through tools for product search, adding items, setting quantities, and checking connection and usage status. Supports Woolworths today, with Coles, Amazon Australia, Kmart and BIG W planned.
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources