Skip to main content
Glama
falkenslab

h5p-mcp

by falkenslab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to h5p-mcp

No user-submitted related servers found.

    Related Servers

    • ricoberry-mcp

      doc-shashank
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to programmatically create, validate, store, and hot-swap interactive quizzes and study bundles into a desktop learning application, with analytics and local REST integration.
      MIT

    • htmlppt

      HappyLiang12
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to create, inspect, and edit self-contained HTML presentation decks through semantic tools, validate them against the htmldeck/v1 contract, hand them to a local visual editor, and export them as standalone HTML, PDF, or per-slide PNG.
      MIT

    • hwp-mcp-old-hangul

      duomo77
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read and edit Korean HWP/HWPX documents, including converting Hanyang PUA old-Hangul characters to Unicode jamo, diagnosing unsupported characters, and preserving arae-a, panch'im, yet-ieung, expanded jamo, filler and side dots. Also supports HWPX search-and-replace, template filling, paragraph/table/image/style editing, page rendering to SVG/HTML, and creating new HWPX documents.
      1
      MIT

    • DJAI Tools MCP

      lovecatisgood-sudo
      A
      license
      A
      quality
      D
      maintenance
      Provides AI agents with local file-processing capabilities for token counting, RAG chunking, CSV/JSON conversion, QR generation, and more, while keeping documents private on the user's machine.
      7
      1
      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.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: listing supported H5P types and their field schemas, building a package, reading an existing package, and reporting server metadata. There is no overlapping behavior that would make tool selection ambiguous.

    Naming Consistency4/5

    Three core tools follow a clear verb_noun_h5p pattern (list_h5p_types, build_h5p, read_h5p), making their relationship obvious. server_info is a minor deviation, but the overall convention remains readable and predictable.

    Tool Count5/5

    Four tools are well-scoped for a package builder: schema discovery, build, read, and server metadata. No tool feels redundant, and the surface is compact without being thin.

    Completeness4/5

    The core lifecycle of discovering types, building validated packages, and reading packages is covered. Upload/deployment is explicitly out of scope, but the surface otherwise lacks no obvious operation needed for content-only package work.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources