Skip to main content
Glama
AesirKode

enhanced-filesystem-mcp

by AesirKode

Related Servers

Alternatives to enhanced-filesystem-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      5 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A 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
      -
    • F
      license
      Not graded
      quality
      F
      maintenance
      A 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
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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.
      13
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform extensive Windows system administration, file operations, process management, network configuration, registry editing, GUI automation, and more through a comprehensive set of MCP tools.
      1
      MIT

    TDQS

    B3.2/5.0

    Scored across 26 tools

    Disambiguation3/5

    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.

    Naming Consistency2/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues