SCORM Packager (HTML → SCORM 2004) MCP Server

What the code does

We read the source, 3 d ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

      await fs.writeFile(outputPath, result.zip);

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        const inputPath = path.join(tmp, safeName);

    execFile(cmd, args, { maxBuffer: 8 * 1024 * 1024 }, (err, stdout, stderr) => {

    document.write('<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/scorm2004.min.js"><\/script>');

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add scorm-mcp-server -- npx -y scorm-mcp-server

{
  "mcpServers": {
    "scorm-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "scorm-mcp-server"
      ]
    }
  }
}

[mcp_servers.scorm-mcp-server]
command = "npx"
args = ["-y", "scorm-mcp-server"]

{
  "mcpServers": {
    "scorm-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "scorm-mcp-server"
      ]
    }
  }
}

{
  "servers": {
    "scorm-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "scorm-mcp-server"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: SCORM_OUTPUT_DIR (Absolute path of the folder where generated SCORM .zip packages are written. Defaults to the current working directory).