Skip to main content
Glama
SagaPeak

Artifacta MCP Server

by SagaPeak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Artifacta MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      16 npm
      MIT

    • artifact-site

      lexmount
      A
      license
      A
      quality
      A
      maintenance
      One place for every AI agent's pages and docs. Publish HTML, build folders, ZIPs, PDFs and Office documents as sandboxed, versioned share links, then search, read and update them later from any MCP client. Sign in with Google or GitHub via OAuth. Open source and self-hostable: https://github.com/lexmount/artifact-site
      26
      16
      Apache 2.0

    • mcp-artifact-store

      prasunraj726-ui
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables multi-agent systems to store large tool outputs and share only artifact IDs between agents, with access control, TTL, and audit logging.
      -

    • 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

    • Stela

      kdowding
      A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted MCP server for publishing, sharing, and reviewing AI agent artifacts with version history and pinned comments.
      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.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct purpose: upload (store_artifact vs request_upload_url/complete_upload), download (get_artifact_download_url vs get_artifact for metadata), listing (list_artifacts vs list_sessions), and identity (whoami). No overlaps.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., complete_upload, get_artifact, list_artifacts, store_artifact). Even 'whoami' fits as a verb phrase.

    Tool Count5/5

    With 8 tools, the set is well-scoped for an artifact management server. Each tool covers a necessary operation without bloat.

    Completeness4/5

    Core lifecycle operations (upload, download, list, retrieve metadata) are covered, but missing update and delete tools, which is a minor gap.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources