Skip to main content
Glama
Polarts

fs-mcp

by Polarts

Related Servers

Alternatives to fs-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      Enables file system operations such as listing, reading, and creating files within a scoped local project directory. It provides a secure way to manage local files through standardized MCP tools built with FastMCP.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables reading, creating, and editing files on the local filesystem through operations like view, create, string replacement, and line insertion.
      78 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local Files MCP server that lets MCP-compatible clients read, search, and modify files inside a sandboxed directory. Provides file management and coding workflow tools with security controls like path boundary enforcement and disabled deletion by default.
      MIT

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct filesystem operation: listing, reading, creating, editing, deleting, and searching. There is no meaningful overlap between grep and read_file, or between create_file and edit_file, so an agent can reliably select the right tool.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun snake_case pattern: explore_filesystem, edit_file, create_file, delete_file, read_file. The one exception is 'grep', which is a conventional command name but slightly breaks the verb_noun pattern.

    Tool Count5/5

    Six tools is a well-scoped set for a filesystem server. Each tool covers a distinct core operation without redundancy or bloat, fitting comfortably within the ideal 3-15 tool range.

    Completeness4/5

    The server covers the full basic lifecycle: list, read, create, edit, delete, and search. Minor gaps exist such as rename/move and file metadata/stat operations, but these can be worked around with existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues