Skip to main content
Glama
lexmount

artifact-site

by lexmount
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to artifact-site

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.
      1
      MIT

    • Artifacta MCP Server

      SagaPeak
      A
      license
      A
      quality
      B
      maintenance
      The artifact store for AI agents. Every output your agents produce — persisted, retrievable, shareable. Across runs, sessions, and tools. Session/agent metadata, content-hash dedup, and expiring share links; available on npm (@artifacta-mcp/mcp) and PyPI (artifacta-mcp).
      8
      1
      MIT

    • artifacty

      raeseoklee
      A
      license
      Not graded
      quality
      A
      maintenance
      A local, agent-to-agent artifact exchange for LLM workflows. Enables MCP-capable tools like Claude, Codex, and Gemini to publish, list, read, update, and continue from artifacts without copying content through chat.
      13 npm
      MIT

    • serve-mcp

      saidmukhamad
      A
      license
      A
      quality
      C
      maintenance
      A local MCP-controlled artifact shelf for agents to publish generated content with stable preview URLs. Provides a shared SQLite registry and HTTP gallery for human browsing.
      3
      11 npm
      1
      MIT

    • agentdrive

      tokencanopy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to store, version, browse, search, and share artifacts in workspace drives and folders through MCP tools, with keys that gate which tools are offered. Uploads produce shareable public links and rendered previews, and the same bearer key works across the REST API and MCP transport.
      Apache 2.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 26 tools

    Disambiguation4/5

    Most tools target a distinct resource/action pair, but publish/update/edit and read/export/get_site have overlapping boundaries that rely on subtle distinctions. The detailed descriptions help, but an agent could misselect between whole-artifact update and single-file edit.

    Naming Consistency4/5

    The artifact_site_ prefix is used consistently, but suffixes mix verb forms (publish, read, export) with noun forms (connection, folders, get_site) and plural/singular comment_ vs comments_. Still readable and mostly predictable.

    Tool Count2/5

    At 26 tools, the set exceeds the 25+ threshold considered too many. The broad domain justifies some size, but the large surface adds selection complexity and feels heavier than a typical well-scoped server.

    Completeness4/5

    The artifact lifecycle is thoroughly covered: publish, update, edit, delete, rollback, fork, move, share, export, uploads, and version inspection. Gaps include no comment creation/reply tools and no explicit share revocation, but core workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources