SCORM Packager (HTML → SCORM 2004) vs Filesystem
A side-by-side look at the SCORM Packager (HTML → SCORM 2004) and Filesystem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SCORM Packager (HTML → SCORM 2004) for education work as a local process; choose Filesystem for file systems as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose SCORM Packager (HTML → SCORM 2004) when
- You need dedicated capabilities in the Education domain.
- You prefer a local stdio subprocess transport.
Choose Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
path, head, tail.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Education | File Systems |
| Quality signal | 43/100 · Fair | 85/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 6 | 91,512 |
| Directory activity | 2 views 0 installs 0 upvotes | 10 views 0 installs 0 upvotes |
| Tools | Not listed | 17 |
| Full listing | View SCORM Packager (HTML → SCORM 2004) | View Filesystem |
Tools & capabilities
SCORM Packager (HTML → SCORM 2004) tools
No tool names declared yet. Check the project README from the listing page.
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SCORM Packager (HTML → SCORM 2004)
{
"mcpServers": {
"scorm-packager-html-scorm-2004": {
"command": "npx",
"args": [
"-y",
"scorm-mcp-server"
]
}
}
}
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
Frequently asked questions
SCORM Packager (HTML → SCORM 2004) is categorized under Education and uses a local stdio subprocess. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick SCORM Packager (HTML → SCORM 2004) for education work and Filesystem for file systems.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
SCORM Packager (HTML → SCORM 2004) has no declared pricing — check the project's own site. Filesystem is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add scorm-packager-html-scorm-2004 and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SCORM Packager (HTML → SCORM 2004) has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 6 GitHub stars. Filesystem has 85/100 (Excellent) with 10 views, 0 installs and 91,512 GitHub stars.