Skip to main content
Glama
tempmd

tempmd-mcp

by tempmd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to tempmd-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • htmldrop

      vin-spiegel
      A
      license
      A
      quality
      A
      maintenance
      Publish HTML or markdown artifacts (reports, dashboards, demos) as instant shareable links with TTL expiry, social preview cards, and optional password protection. Works with the hosted service or a self-hosted instance.
      1
      5 npm
      13
      MIT

    • sentou

      TrueLineCollective
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables publishing and updating Claude artifacts or HTML to private, access-controlled links directly from Claude.
      1
      AGPL 3.0

    • @share-html/mcp-server

      arunai30
      A
      license
      A
      quality
      B
      maintenance
      Enables publishing sanitized static HTML pages from an MCP agent and receiving shareable URLs, with tools for updating, listing, publishing, and deleting pages.
      12
      5 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

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct operation: lifecycle check, local listing, publishing new, restoring expired, toggling comments, freezing snapshot, and updating existing. No functional overlap; clear boundaries.

    Naming Consistency5/5

    All tools follow the snake_case verb_noun pattern (e.g., get_temp_status, publish_temp, snapshot_temp). No deviations or mixed conventions.

    Tool Count5/5

    Seven tools cover the full lifecycle of temporary artifacts without bloat. The count feels right for the domain—neither too sparse nor excessive.

    Completeness4/5

    Core CRUD-like operations are covered (create via publish, read via get_status/list, update via update_temp, plus restore and snapshot). A delete tool is missing, but the domain may intentionally avoid deletion (temps expire naturally). Minor gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources