Skip to main content
Glama
Sign In
akshat12000

File System Explorer MCP Server

by akshat12000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to File System Explorer MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Learning Project

      RobertBauer-dev
      F
      license
      Not graded
      quality
      D
      maintenance
      A tutorial MCP server for learning the Model Context Protocol by building file and system tools. Provides hands-on experience creating custom tools that enable AI models to interact with files and execute system commands.
      -

    • Agentic Terminal

      mohamedmahmoud8801
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that gives AI agents terminal execution, Python scripting, file management, and code search tools so they can carry out real development tasks. It exposes bash, Python, glob, grep, and file/folder operations over MCP for coding assistants and codebase exploration.
      9
      1
      MIT

    • mcp-file-manager

      AMEOBIUS-space
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI agents file system access: read, write, search, hash, directory trees — 12 tools, zero dependencies, pure Python stdlib.
      MIT

    • MCP AI Developer Agent

      bhavya681
      A
      license
      Not graded
      quality
      D
      maintenance
      An AI-powered developer assistant MCP server that provides filesystem tools (list_files, read_file, search_files, write_file) to help AI agents inspect, analyze, and modify real codebases via the Model Context Protocol.
      3,240 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: get_file_info retrieves metadata, list_directory shows directory contents, read_file accesses file data, and search_files performs pattern matching. An agent can easily distinguish between these operations.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case naming (get_file_info, list_directory, read_file, search_files). The naming is predictable and readable throughout the set.

    Tool Count4/5

    Four tools is reasonable for a file system explorer, covering core operations like inspection, listing, reading, and searching. It feels slightly minimal but well-scoped for basic file system interactions.

    Completeness3/5

    The tools cover read-only operations well but lack write capabilities (e.g., create, update, delete files/directories) and advanced features like file watching or permissions management. This is a notable gap for a full file system explorer.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources