Skip to main content
Glama
j0hanz

filesystem-mcp

by j0hanz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to filesystem-mcp

No user-submitted related servers found.

    Related Servers

    • Filesys

      YothisisTroy
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A Filesystem MCP server that allows an LLM to read and list files from a specified directory on your local machine through the Model Context Protocol.
      2
      -

    • mcp-coding

      cdemeo92
      A
      license
      Not graded
      quality
      D
      maintenance
      Experimental MCP server for local LLM orchestration with filesystem tools (read, write, list, delete files) and a CLI agent that communicates via Ollama.
      2 npm
      ISC

    • emcp

      slezica
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing filesystem operations, shell execution, and web search capabilities.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct file system operation — listing, reading, writing, editing, moving, diffing, searching, etc. Even overlapping operations like edit vs replace_text are clearly differentiated by scope (literal sequential vs bulk regex) and search_text vs find_files by content vs filename. No ambiguity remains.

    Naming Consistency4/5

    Most tools follow a clear verb or verb_noun pattern (create, delete, read, list_roots, search_text). The only deviation is the mix of single-word verbs (list, diff, stat) and compound verbs (replace_text, find_files), but all use snake_case consistently, making the set predictable.

    Tool Count5/5

    13 tools is well-scoped for a filesystem server. Each tool has a distinct purpose and none feel redundant. The count covers the breadth of file operations without excessive granularity or missing essentials.

    Completeness5/5

    The tool surface covers the full file lifecycle: create, read, edit, patch, move (with copy), delete, plus metadata (stat), listing (list/find), search, and root discovery. Operations are logically paired (e.g., diff and patch enable safe application of changes), and bulk variants exist for efficiency. No obvious gaps that would break agent workflows.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources