Skip to main content
Glama

Related Servers

Alternatives to mcp-file-tools

  • A
    license
    B
    quality
    D
    maintenance
    A read-only MCP server that provides document awareness for agents by parsing local files into structured profiles, blocks, chunks, and search results, enabling agents to understand and cite document content without dealing with raw file formats.
    5
    30 npm
    3
    Apache 2.0

Related Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    MCP server for encoding-aware file operations supporting 168 encodings, with secure directory-restricted tools and optional local execution for ChatGPT Web via OpenAI Secure MCP Tunnel.
    1
    GPL 3.0
  • A
    license
    A
    quality
    A
    maintenance
    Comprehensive MCP server for filesystem operations, process management, interactive sessions, and async file search. Includes utilities for JSON repair, encoding fixes, duplicate detection, OCR, ZIP archives, and Markdown export.
    6
    46
    274 npm
    4
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    MCP server for full lifecycle of 1C binary files (CF/CFE/EPF/ERF) without EDT import: unpack to a temporary directory, read and edit code/forms/help, search, diff, repack, and cleanup. Enables code analysis, patching, and bytecode decompilation of protected modules via natural language.
    20
    5
    MIT

TDQS

A4.4/5.0

Scored across 20 tools

Disambiguation5/5

Each tool targets a distinct operation: read vs write vs edit vs delete, encoding detection vs conversion vs BOM/line-ending management, filename search vs content grep, directory listing vs tree view. Even closely related tools (read_text_file vs read_multiple_files) are clearly separated by cardinality, and descriptions emphasize when to prefer one over another.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (create_directory, convert_encoding, manage_bom, read_text_file). Even 'tree' fits as a command-style noun, and the pattern is predictable across the entire set.

Tool Count4/5

20 tools is at the upper edge of typical scope, but the domain of file manipulation with encoding/line-ending/BOM handling justifies the breadth. Each tool addresses a specific need without redundancy, and the count feels appropriate for a comprehensive file toolkit.

Completeness5/5

The surface covers the full lifecycle: create, read (single/multiple), update (edit/write), delete, copy/move, search (filename/content), metadata, directory traversal, and encoding/BOM/line-ending utilities. No obvious dead ends—even edge cases like batch conversions and paging reads are handled.

Maintenance

ActivityActive
ResponsivenessSlow