Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to WebCake Storefront MCP

No user-submitted related servers found.

    Related Servers

    • sbuilder-mcp

      vuluu2k
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to operate a Store Builder site end-to-end — designing pages, filling them with data, reviewing screenshots, and publishing — without human intervention.
      37
      970 npm
      MIT
    • PromptSwing by PromptSwing

      PromptSwingofficial

      PromptSwing
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI assistant to publish a storefront it built to live hosting, read the live site back, add, update or delete a single page, manage the catalogue, orders and reviews, and restore any earlier version in one call. Hosting requires a paid subscription, and a free pre-publish assessment reports which documented signal calls, contrast pairs or hardcoded prices would fail.
      19 npm
      Apache 2.0
    • RedStudio MCP by REDStudioOrg

      RedStudio MCPofficial

      REDStudioOrg
      A
      license
      A
      quality
      C
      maintenance
      Lets AI assistants publish and edit pages, components, media and blog posts on a hosted RedStudio website, with shop, Stripe payments, bookings and event tickets included. Site settings, redirects, booking hours and revisions are all managed through the assistant instead of a separate backend.
      29
      302 npm
      MIT
    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

    B3.3/5.0

    Scored across 131 tools

    Disambiguation4/5

    Most tools have sharply distinct resource+action targets, and descriptions explicitly cross-reference alternatives (e.g. edit_http_function vs update_http_function, create_page vs build_page, update_page_element vs update_page_elements vs update_page_source). The main overlap risk is the parallel 'global source' (cart/popup) and 'global section' (header/footer) families plus their element/section/content variants, which a hurried agent could confuse, but the naming and descriptions do provide workable boundaries.

    Naming Consistency4/5

    The set overwhelmingly follows a snake_case verb_noun convention (list_products, create_article, update_global_source_element, delete_collection). A few names invert the order (get_source_cart) or use bare plurals (search_images, upload_images), and there is a large cluster of very long compound names, but the pattern remains predictable and readable.

    Tool Count1/5

    131 natively exposed tools is an extreme over-scoping for a single server surface, well beyond the healthy 3-15 range. Even though a search_tools/invoke_tool mechanism exists for on-demand discovery, the native list itself is unwieldy and far exceeds any reasonable curated tool set.

    Completeness4/5

    The surface covers the full site-building lifecycle with strong CRUD for products, categories, articles, pages, collections, global sections/sources, themes, customers, promotions and orders, plus versioning, publishing and image hosting. Minor gaps exist (e.g. orders are read-only list/get with no update or manual create), but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources