Skip to main content
Glama
Frosty-09

Qwen MCP Filesystem Server

by Frosty-09
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Qwen MCP Filesystem Server

No user-submitted related servers found.

    Related Servers

    • MCP-FileSystem

      dgholamian
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that gives AI assistants secure, sandboxed filesystem access with tools for reading, writing, searching, and managing files and directories.
      MIT

    • MCP Local File Reader

      sworddut
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that allows AI models to safely access and interact with local file systems, enabling reading file contents, listing directories, and retrieving file metadata.
      2 npm
      10
      MIT

    • LocalBridge

      ysunyang979-sys
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to securely inspect, search, edit, build, and test explicitly authorized local development projects over MCP, with sandboxed filesystem access and sensitive-file protection.
      2
      Apache 2.0
    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

    A3.5/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource type: project-level status/list/create/register/resolve versus file-level list/read/write/append/delete/rename/search. There is no meaningful overlap between the tools, and the descriptions reinforce their boundaries.

    Naming Consistency5/5

    All tools follow the same qwen_verb_noun pattern, with clear verbs like create, list, read, write, append, delete, rename, and search. The naming is uniform and predictable across the entire tool set.

    Tool Count5/5

    12 tools is well within the ideal range for a filesystem server. Each tool covers a necessary operation without redundancy or bloat, and the set feels appropriately scoped for managing projects and their files.

    Completeness4/5

    File operations are well covered with create, read, update, append, delete, rename, and search. The main gaps are project lifecycle operations: there is no delete/unregister project tool, and no explicit directory creation tool, though these are minor for the core file-management purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources