SEAL (sealnet-mcp) vs draw.io MCP (official)
Both are files & office documents MCP servers, and we ran both through the same test (diagram reference, share manage) in each app. SEAL (sealnet-mcp) passed 3 of 3 apps we tested it in; draw.io MCP (official) passed 2 of 4.
Test results side by side
| SEAL (sealnet-mcp) | draw.io MCP (official) | |
|---|---|---|
| Claude Code | Passed 2026-10-22 | Partial 2026-10-15 |
| Cursor | Passed 2026-10-22 | Partial 2026-10-15 |
| Claude Desktop | Not tested yet | Passed 2026-10-21 |
| ChatGPT (Codex) | Passed 2026-10-22 | Passed 2026-10-21 |
| Tools exposed (protocol check) | 8 tools | 8 tools |
| GitHub stars | 0 (shared repo) | 5,642 |
| License | Proprietary (npm: UNLICENSED) | Apache-2.0 |
| 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
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.
draw.io MCP (official): The draw.io team's own MCP for opening diagrams (XML, CSV, Mermaid) and reading draw.io shape/reference docs.
