vulcan-file-ops
Related Servers
Alternatives to vulcan-file-ops
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude Desktop to perform file operations like reading, writing, listing directories, and managing files through natural language commands.MIT
- AlicenseNot gradedqualityFmaintenanceA comprehensive MCP (Model Context Protocol) server for file system operations, providing Claude and other AI assistants with access to local files and directories.2MIT
- AlicenseNot gradedqualityBmaintenanceA sandboxed file-access MCP server for Claude Desktop, enabling safe read/write access to selected directories with atomic verified writes, undo, and read-only git operations.1MIT
- AlicenseNot gradedqualityDmaintenanceIntegration project for Model Context Protocol (MCP) servers with Claude Desktop App, enabling filesystem operations, development support, and file management through natural language.MIT
- AlicenseNot gradedqualityCmaintenanceA production-ready MCP server enabling Claude and other LLMs to perform intelligent file operations with minimal token usage.MIT
- AlicenseNot gradedqualityDmaintenanceA filesystem Model Context Protocol server that provides Claude Desktop with capabilities to read, write, and manipulate files on your system.12 npmMIT
TDQS
Scored across 17 tools
Most tools target distinct file operations, but a few boundaries blur: move_file overlaps with file_operations (which also moves/renames), and list_directory's tree mode overlaps with glob_files for recursive listing. Descriptions clarify single-vs-bulk and listing-vs-pattern use, so misselection is limited.
Names are uniformly snake_case and nearly all follow verb_noun (read_file, write_multiple_files, list_directory). The outlier is file_operations, a noun phrase rather than an action verb, and list_allowed_directories inserts an adjective, but overall the pattern is predictable.
17 tools is slightly above the ideal 3-15 range but each tool has a clear role in a full filesystem server. Batch/single variants and specialized tools like attach_image and register_directory justify their place, with no obvious filler.
The surface covers the full filesystem lifecycle: create, read, write, edit, move, copy/rename (via file_operations), delete, list, glob/grep search, metadata, plus shell execution and directory access management. No critical gaps remain for typical file operations.