---
title: "Scorm Mcp Server"
description: "This is a packager aimed squarely at a 2026 problem: an LLM or a design tool has produced a self-contained HTML module, and it now needs to import into an LMS. Point the scorm_package tool at a file, folder or zip and you get a PIF zip back — assets inlined so nothing is fetched at run time, a tracking runtime injected, and a manifest validated against the bundled ADL schemas rather than merely checked for well-formedness."
canonical_url: "https://scorm-tools.com/tools/scorm-mcp-server"
last_updated: "2026-10-31T10:22:03.331Z"
---

This is a packager aimed squarely at a 2026 problem: an LLM or a design tool has produced a self-contained HTML module, and it now needs to import into an LMS. Point the `scorm_package` tool at a file, folder or zip and you get a PIF zip back — assets inlined so nothing is fetched at run time, a tracking runtime injected, and a manifest validated against the bundled ADL schemas rather than merely checked for well-formedness.

The runtime is version-adaptive: it binds to whichever API the host exposes, `API_1484_11` or `API`, and maps the data model accordingly — one `lesson_status` and a 0–100 score under 1.2, split completion and success under 2004. That is the right design for a wrapper, and it is tested; the repository carries a large suite covering the converter, the runtime and schema conformance.

Judge it as a young project, because it is one. First commit July 2026, a handful of stars, one maintainer, and the detailed handover documentation is in French. The maintainer's own conformance evidence is an import into SCORM Cloud, which is meaningful but is not certification.

It is not an authoring tool and does not attempt cmi5 or xAPI. If your content is already built and your only remaining problem is the wrapper, it is a reasonable, inspectable choice — with the caveat that the bus factor is one.