Skip to main content
Glama
Preston-Harrison

Filesystem MCP Server

Related Servers

Alternatives to Filesystem MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides secure, sandboxed filesystem operations including reading, writing, listing, searching, and managing files and directories within a configurable working directory with strict security controls.
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides sandboxed access to local filesystem operations including directory and file management, content search with glob and regex patterns, and binary file support with configurable safety limits.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides secure file system operations for AI assistants including directory listing, file reading/writing, deletion, searching, and copying. Features safety controls like path validation, permission checks, and file size limits.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely read, write, and search files within a whitelisted sandbox directory, rejecting any attempts to escape the sandbox.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides safe filesystem access for AI clients with root confinement, read-only mode, and file operations like read, write, search, copy, move, delete.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides secure file read and write operations within a sandboxed directory, allowing AI assistants to safely create, modify, and access files without risk of accessing the broader file system.
      -

    TDQS

    A4.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no significant overlap. For example, create_directory vs. create_file, read_text_file vs. read_multiple_files, and search_files vs. grep all target different operations. The descriptions clearly differentiate their specific functions, making tool selection unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case throughout, such as create_directory, list_directory, and read_text_file. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.

    Tool Count5/5

    With 12 tools, the server provides a well-scoped set for filesystem operations, covering creation, deletion, reading, editing, searching, and listing. Each tool serves a specific and necessary function without redundancy, making the count appropriate for the domain.

    Completeness5/5

    The tool set offers comprehensive coverage for filesystem management, including CRUD operations (create, read, edit, delete), navigation (list, tree), and advanced features (search, grep, move). There are no obvious gaps; agents can perform all typical filesystem tasks without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues