fsext-mcp-server-python
Related Servers
Alternatives to fsext-mcp-server-python
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA full-featured secure MCP server for local file system operations, with built-in image processing, OCR and media tools.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceA secure Model Context Protocol server providing HTTP endpoints for AI agent tool execution, including file system operations, shell commands, and LLM-based code generation.1-
- AlicenseNot gradedqualityBmaintenanceGives MCP-compatible AI clients a controlled bridge to local files, processes, search, and document utilities, including reading/writing and moving files, text block editing, directory listing, content search, starting and managing terminal processes, and PDF/Excel/DOCX/image handling. It serves these tools over MCP Streamable HTTP at a configurable endpoint, with optional Bearer-token authentication and read-only or restricted-directory modes for safer remote exposure.1MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol server implementation that enables AI assistants to interact with file systems, databases, GitHub repositories, web resources, and system tools while maintaining security and control.28 npm2MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that enables AI assistants to perform comprehensive file operations including finding, reading, writing, editing, searching, moving, and copying files with security validations.71-
- AlicenseNot gradedqualityDmaintenanceA production-ready Model Context Protocol suite over Streamable HTTP providing a sandboxed file server with tools, resources, prompts, and both manual and AI-driven clients.MIT
TDQS
Scored across 22 tools
Most tools are clearly distinct, but the three search tools (fs_search_files_by_content, fs_search_in_files_by_content, fs_search_in_file_by_content) have highly overlapping descriptions and could easily be misselected. Additionally, fs_read_full_text and fs_read_text_range are similar, though they differ by range.
The 'fs_' prefix is consistent, and most tools follow a verb_noun pattern (e.g., fs_delete_file, fs_create_file). However, image tools use noun_verb (fs_image_resize, fs_image_crop) and fs_ocr_extract_text deviates, while fs_is_file_exists uses a predicate structure. This mixed convention creates inconsistency.
With 22 tools, the server is slightly heavy but each tool fills a specific niche (files, directories, text, binary, search, images, OCR). The count is on the higher end of reasonable but not excessive for the broad domain.
File operations are well-covered, but directory operations are missing create and delete functionality. There is no fs_create_directory or fs_delete_directory, which forces agents to work around these gaps. This is a significant omission for a filesystem server.