What this is

A self-hosted H5P authoring and generation stack. AI agents build .h5p packages through MCP tool calls; a local engine and editor handle editing and playback. No cloud, no API keys, no manual H5P editor.

Why it was built

The cloud LMSable generator produces .h5p files that fail to import into the target LMS with:

api-version-unsupported (current: 1.27, required: 1.28)

LMSable packages pin their libraries to H5P core API 1.28, but the LMS (Lumi and the WordPress H5P plugin) runs core 1.27. Self-hosting gives us control of the library versions.

Components (under D:/edu/h5p)

• MCP server (h5p-mcp-server) - port 3000 (HTTP) or stdio - MCP tools that build .h5p from agent-written content.
• H5P engine (h5p-nodejs-library) - port 8080 - full H5P editor / playback server (core 1.28).
• Lumi AI editor (lumi-ai-editor) - port 3039 - AI worksheet editor frontend (Vite dev).
• Offline player (not wired yet) - h5p-player web component, no backend.

The MCP server

• TypeScript + @modelcontextprotocol/sdk 1.32 + fflate.
• Logic in src/h5p.ts; MCP wrapper in src/server.ts.
• Libraries sourced from Lumi's 144-library bundle (core 1.27), so packages import into any LMS.
• Three tools: h5p_list_content_types (54 types), h5p_get_schema, h5p_build_package.
• Dual transport: stdio (spawned clients) and Streamable HTTP (shared service for LM Studio and remote agents).

Key decisions

• H5P core 1.28 via H5P-Nodejs-library master (the npm release still pins 1.27).
• MCP is the integration surface - AI studios and agents write the content themselves.