vs Ultra
Feature Comparison
Section titled “Feature Comparison”| Feature | This server | Ultra |
|---|---|---|
| Tools | 18 + 3 aliases + help | 16 (consolidated) |
| Normalizer | Yes (ported) | Yes (original) |
| MCP Roots | Yes | Partial |
| Tool Annotations | Yes (all tools) | Partial |
| Media file reading | Yes (read_media_file) | No |
| Atomic writes | Yes (all write ops) | Yes |
edit_file dry run | Yes | No |
| Backup/restore | No | Yes |
| Pipeline executor | No | Yes |
| Audit trail | No | Yes |
| Regex edit mode | No | Yes |
| WSL integration | No | Yes |
| Hooks system | No | Yes |
| Dashboard | Yes (logdashboard) | Yes |
| Streaming | No | Yes |
| Official MCP aliases | Yes (3) | No |
When to use this server
Section titled “When to use this server”- You want a simple, lightweight MCP filesystem server.
- You don’t need backup/restore, pipelines, or WSL.
- You want the normalizer intelligence without the extra features.
- You need compatibility with clients trained on the official MCP filesystem server.
- You prefer focused tools (18) over consolidated ones (16 in ultra).
When to use ultra
Section titled “When to use ultra”- You need backup/restore for safe editing workflows.
- You use WSL and need cross-environment file access.
- You want pipeline execution for complex multi-step operations.
- You need audit trails and dashboards for monitoring.
- You want streaming for large file operations.
Migration
Section titled “Migration”Both servers use the same MCP protocol and normalizer layer. Tool names differ — ultra consolidates operations into fewer, more powerful tools. There is no automated migration path; reconfigure your MCP client to point to the other server.