enhanced-filesystem-mcp
Related Servers
Alternatives to enhanced-filesystem-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to securely control and interact with a local Windows machine through 218 configurable tools for files, Git, processes, Windows UI, browser automation, WSL, Office, recovery, skills, and child MCP servers.7 npmMIT
- FlicenseNot gradedqualityFmaintenanceA powerful filesystem MCP server for AI agents with extensive system access, including filesystem operations, shell execution, Windows tools, reverse engineering, code intelligence, and agent orchestration.1-
- FlicenseNot gradedqualityFmaintenanceA lightweight MCP HTTP server giving AI assistants real tools to interact with your Windows machine, including running commands, file access, system info, web search, and browser automation.1-
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server that enables AI agents to seamlessly integrate with Windows, performing tasks like file navigation, application control, UI interaction, and QA testing.1MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted server that lets ChatGPT, Grok, and stdio MCP clients read and write files, run PowerShell/CMD and interactive processes, and drive the Windows desktop through screenshots, window info, clicks, drags, and keyboard input. It connects via OpenAI Secure MCP Tunnels, an OAuth authorization-code + S256 PKCE HTTPS endpoint, or local stdio, exposing 38 tools under the user's own Windows account.MIT
- AlicenseNot gradedqualityCmaintenanceA MCP server for Windows/Linux that provides 90+ tools enabling AI assistants to systematically manage local systems, including system probing, command execution, file editing, network diagnostics, and more.13MIT
TDQS
Scored across 26 tools
Most tools have clearly distinct purposes, but efs_batch duplicates operations in efs_read/write/edit/delete/move/list, creating ambiguity about when to use batch versus individual tools. JSON and YAML tools overlap on JSON handling, and efs_exec/process_tool have unclear boundaries for shell versus process management.
The efs_ prefix is used for filesystem operations but also for git, exec, and python tools, making the prefix meaningless. Other tools use a '_tool' suffix with varied noun names, mixing snake_case conventions and creating two completely different naming patterns.
26 tools is excessive for a filesystem-focused server, especially since many tools (ollama, http, windows automation, ssh) are unrelated to files. The broad scope makes the set feel like a grab-bag rather than a cohesive toolset.
Core filesystem operations like read, write, edit, delete, move, list, and search are covered, but there is no copy tool, no chmod or symlink support, and efs_git includes only a subset of git commands. The non-filesystem tools feel bolted on and do not fill these primary domain gaps.