Skip to main content
Glama
stevysmith

stacktree-mcp

by stevysmith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to stacktree-mcp

No user-submitted related servers found.

    Related Servers

    • portego

      laguna-engineering
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets MCP clients upload, list, and retrieve HTML artifacts and their metadata, including submitting files via signed upload tickets.
      1
      Apache 2.0

    • open-artifacts

      emaxe
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to publish, retrieve, update, and delete hosted HTML, Markdown, Mermaid, and SVG artifacts and to create, list, or revoke shareable links through authenticated, scope-enforced tools. It exposes artifact hosting over Streamable HTTP so any MCP client can manage content on a self-hosted instance using a Bearer agent API key.
      MIT

    • sentou

      TrueLineCollective
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables publishing and updating Claude artifacts or HTML to private, access-controlled links directly from Claude.
      1
      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.1/5.0

    Scored across 25 tools

    Disambiguation3/5

    Most tools have clearly separated lifecycle roles, but get_site and get_content overlap almost exactly: both return the exact stored HTML of an owned page and both point to update_site. set_client and create_client_space also engage similar auto-create behavior, though their primary intents differ. The verbose descriptions rescue most boundaries, so this is partial overlap rather than chaos.

    Naming Consistency5/5

    Every tool follows a consistent lowercase snake_case verb_noun pattern: get_, list_, create_, update_, delete_, set_, publish_, restore_, revoke_, link_. The verbs are standard and the objects are predictable resources like site, client_space, share_link, feedback, password, and expiry. Minor semantic redundancy like get_site vs get_content does not break the naming convention.

    Tool Count3/5

    25 tools sits at the top of the heavy band, and the set includes a duplicate reader plus rarely-needed helpers like create_client_space that publish_html can auto-trigger. The broad platform scope justifies many of the tools, but the surface feels slightly over-provisioned for an agent to navigate. It is not egregious, but it is not a tight 3-15 tool set.

    Completeness5/5

    The page lifecycle is fully covered: publish, read, update, delete, restore, list, claim, expiry, access gates, and share links. Client spaces have create/list/update/delete plus assignment, and the feedback loop is complete with toggle, list, and resolve. Account/wallet and design-guidance tools round out the domain with no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources