file_utils MCP
Related Servers
Alternatives to file_utils MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server for precise, hash-referenced file editing that enables atomic edits using line:hash references instead of fragile line numbers or full content reproduction.2-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides line-oriented text file editing capabilities through a standardized API. Optimized for LLM tools with efficient partial file access to minimize token usage.MIT
- AlicenseNot gradedqualityDmaintenanceA TypeScript-based MCP server that provides tools for making precise line-based edits to text files within allowed directories.34MIT
- AlicenseNot gradedqualityCmaintenanceAn HTTP MCP server that indexes large documents into exact-line-numbered sections, enabling AI models to locate, read, summarize, and edit parts of a document without ingesting the whole file.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for reading, writing, and editing files on the local filesystem.1,605Apache 2.0
- AlicenseAqualityBmaintenanceAn MCP server that provides surgical read/write access to individual sections of Markdown files, allowing agents to fetch, edit, or delete specific slices without touching the entire file.71MIT
TDQS
Scored across 6 tools
Each tool has a distinct action and target: stripping conflict markers, reading a range, editing a range, inserting at a line, prepending, and appending. No two tools overlap in purpose; even the similar insert/prepend/append are clearly differentiated by operation type and location.
All tool names are snake_case and begin with a verb, but the pattern is inconsistent: some use verb_noun (read_file_range, edit_file_range, strip_conflict_markers) while others use verb_preposition (insert_at, prepend_to_file, append_to_file). This is a minor deviation that could be improved by renaming insert_at to insert_at_line for consistency.
Six tools is a well-scoped set for a file utilities server, covering read, edit, insert, prepend, append, and conflict marker cleanup. It is neither too sparse nor overwhelming, and each tool serves a distinct purpose.
The set covers the core file modification lifecycle: read a range, replace a range, insert line(s), prepend, append, and clean conflict markers. The main gap is the lack of an explicit delete operation, though edit_file_range with empty content can serve that purpose. Minor but workable.