fast-filesystem-mcp
Related Servers
Alternatives to fast-filesystem-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA tuned filesystem MCP server for Codex-style development, offering fast file operations, bounded output, and safe edits.MIT
- AlicenseAqualityDmaintenanceA comprehensive MCP server that enables AI models to perform local file operations, command execution, and task management across multiple platforms. It features advanced capabilities like row-level file editing, directory searching, and system monitoring with built-in security filters.1321 npmMulan Permissive Software , Version 2
- AlicenseAqualityBmaintenanceAn MCP server that implements Claude Code-like functionality, allowing the AI to analyze codebases, modify files, execute commands, and manage projects through direct file system interactions.15304MIT
- AlicenseNot gradedqualityCmaintenanceA drop-in replacement for the blocked Filesystem MCP server that provides standard file operations with symlink hardening, enabling tools like read, write, and directory listing.MIT
- AlicenseNot gradedqualityDmaintenanceA secure MCP server that allows Claude to read and write local files on your machine with explicit approval gating for each access.MIT
- AlicenseCqualityDmaintenanceA comprehensive MCP server that provides AI assistants with tools for file system management, Git integration, and shell command execution. It features specialized code utilities for analysis, formatting, and linting to enhance development workflows within Claude Desktop.287MIT
TDQS
Scored across 25 tools
Most tools are distinct, but there is notable overlap between fast_edit_block, fast_safe_edit, fast_edit_multiple_blocks, and fast_edit_blocks—all handle editing and could confuse an agent. Similarly, fast_search_files and fast_search_code have overlapping purposes despite different descriptions.
The fast_ prefix is applied consistently and most tools follow a verb_noun pattern (e.g., fast_read_file, fast_create_directory). Minor deviations like fast_edit_blocks vs fast_edit_multiple_blocks and fast_batch_file_operations are slightly inconsistent but still readable.
25 tools is at the upper boundary of what is reasonable for a filesystem server. The count feels heavy because several tools overlap (multiple edit variants, two search tools, multiple read/write variants), but each has a plausible use case.
The tool surface covers the full filesystem lifecycle: read, write, edit, list, search, create, copy, move, delete, batch operations, compression, sync, and disk usage. There are no obvious dead ends for common file operations.