Skip to main content
Glama
saidmukhamad

serve-mcp

by saidmukhamad

Related Servers

Alternatives to serve-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
    • A
      license
      A
      quality
      A
      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
    • 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
    • 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

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct action: publish, list, or delete artifacts. There is no overlap in purpose, making it clear which tool to use for each operation.

    Naming Consistency5/5

    All tools follow the consistent 'artifact_verb' pattern in snake_case, making the naming predictable and easy to navigate.

    Tool Count5/5

    With only 3 tools, the server is well-scoped for its purpose: publishing, listing, and deleting artifacts. This is a focused set without unnecessary clutter.

    Completeness4/5

    The set covers core CRUD operations: create/update via artifact_publish, read via artifact_list, and delete via artifact_delete. A minor gap is the lack of a dedicated tool to retrieve a single artifact's details beyond the list.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues