Purpose
ellmos FileCommander MCP Server is a comprehensive local file system MCP (Model Context Protocol) server designed to provide AI assistants with complete access to the local system. Unlike most file system MCP servers that cover only basic read/write, FileCommander integrates 50 tools in a single server, covering file operations, content search, process management, interactive sessions, format conversion, document export, and more.
Main Capabilities
File System Operations (15 tools) Includes file reading, writing, moving, copying, and more. Among them, fc_preview_file is the remote/headless fallback for local files; by default, the call returns only structured metadata (resolved path, file:// URI, MIME type, byte size, preview type, fixed 1 MiB limit, and suggestions for subsequent calls); content is read only after include_content=true. Files over 1 MiB and unsupported types remain in metadata-only mode and are not read or Base64-encoded.
Content Search (1 tool) fc_search_content does not expand wildcards, does not traverse directories, and does not recursively discover files. It accepts at most 50 explicit UTF-8 text files, skips binary files and files larger than 10 MB, and returns deterministic JSON. Globally, there are at most 200 matches, 100 matches per file, 10 lines of context, 500 characters of excerpt, and 200,000 characters of serialized output. Missing, cloud-only, permission, encoding, binary, and size errors are reported per file, readable files can still produce results, and common secret key formats are redacted in excerpts.
Asynchronous Search (5 tools) Supports searching large directory trees in the background while the AI continues working, with pagination and token management.
Process Management (5 tools) Can list, start, and terminate system processes. fc_execute_command accepts arbitrary shell commands (ordinary commands use Node's default shell, which is cmd.exe on Windows; Windows paths with special characters can be routed to Windows PowerShell). fc_start_process allows the caller to choose the executable and arguments. fc_open_path onlyaccepts an existing file or directory and hands it to a fixed native default handler launcher, and its result always reports user_visible as "unknown".
Interactive Sessions (5 tools) Starts and interacts with REPLs (Python, Node.js, Shell, etc.) via the MCP protocol, using a bounded ring buffer.
Other Tools File maintenance and repair (9, including string replacement, JSON repair, Mojibake encoding repair, duplicate detection), archiving (1, ZIP create/extract/list), cloud sync (1), system (4), export (2, Markdown to HTML/PDF). It also supports format conversion (fc_convert_format, lossless conversion among JSON, YAML, TOML, XML, CSV, INI, TOON), checksums (fc_checksum, supporting MD5, SHA-1, SHA-256, SHA-384, SHA-512), and OCR (optional tesseract.js dependency).
Usage
Requires Node.js 20 or higher. It can be installed via NPM (the npm page corresponding to the package name ellmos-filecommander; the specific installation command text is not provided in the materials), or installed from source. The server communicates via stdio transport; in Claude Desktop, configuration must be added in claude_desktop_config.json (on Windows the path is %APPDATA%\Claude\claude_desktop_config.json, on macOS it is ~/Library/Application Support/Claude/claude_desktop_config.json), and the application must be restarted after saving. Other MCP clients can point their entry point to dist/index.js or the ellmos-filecommander binary.
Applicable Scenarios
- Autonomous AI coding agents and LLM clusters: When multi-agent clusters and monolithic agent runtimes (such as Claude Code, Gemini, OpenAI Codex, AutoGen, CrewAI) perform recursive code editing, project refactoring, and directory audits, avoid upThe following process crashes caused by window inflation, file locks in cloud-synced folders, and repository corruption caused by accidental deletion.
- DevOps and multi-host automation engineers: build cross-platform CLI tools, CI/CD validation pipelines, and multi-machine synchronization scripts, unifying Windows, Linux, and macOS semantics.
- Security operations and compliance personnel: require local stdio transport, zero telemetry, zero open network listening ports, and automatic redaction of keys and tokens in search excerpts.
- Enterprise platform architects and data pipeline developers: integrate local files, normalize heterogeneous configuration formats, verify cryptographic hashes, and generate reports.
Limitations
- The server has full file system access with the same permissions as the running user.
- fc_execute_command can run arbitrary shell commands; fc_open_path invokes the application associated with the operating system.
- Outbound network egress is strictly limited to fc_web_fetch actively triggered by the caller, and internal/private IPs are blocked by default.
- Some third-party directories still display the old 43-tool metadata; the official README/npm metadata shall prevail.
- Specific installation commands, configuration code, pricing, platform compatibility details, etc. are not fully provided in the materials and are subject to the official repository.
