Filesystem (reference) vs SEAL (sealnet-mcp)
Both are files & office documents MCP servers, and we ran both through the same test (share manage, write read back) in each app. Filesystem (reference) passed 4 of 4 apps we tested it in; SEAL (sealnet-mcp) passed 3 of 3.
Test results side by side
| Filesystem (reference) | SEAL (sealnet-mcp) | |
|---|---|---|
| Claude Code | Passed 2026-10-19 | Passed 2026-10-22 |
| Cursor | Passed 2026-10-19 | Passed 2026-10-22 |
| Claude Desktop | Passed 2026-10-14 | Not tested yet |
| ChatGPT (Codex) | Passed 2026-10-20 | Passed 2026-10-22 |
| Tools exposed (protocol check) | 14 tools | 8 tools |
| GitHub stars | 91,266 (shared repo) | 0 (shared repo) |
| License | NOASSERTION | Proprietary (npm: UNLICENSED) |
| Last push | 2026-10-13 | ? |
Results from our own harness runs, dated per cell. Stars and last push from GitHub at our last data refresh. We don’t pick a winner here: which one fits depends on your app and setup.
What each does
Filesystem (reference): Lets the agent read, write, search and move files, limited to the folders you list in the config.
SEAL (sealnet-mcp): Local MCP server for SEAL's end-to-end encrypted sharing: your agent hands files, folders or secrets to you or another agent as seals, asks you for a file or secret through a dialog or page, and runs commands with secrets kept out of its output. After pairing, the default delivery route sends a file to the user's SEAL inbox and returns a short handle to the model. Free up to 1 GB per seal.
