Skip to main content
Glama

Related Servers

Alternatives to MCP File Compaction

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      maintenance
      Enables local-first AST-based code context pruning for LLMs and AI coding agents, stripping internal function bodies to stubs while preserving signatures, interfaces, type hints, and docstrings to reduce token usage.
      3
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to obtain a compressed code context where the active file is fully included and dependency files are reduced to type signatures, interfaces, and exports, cutting token usage while preserving code shape.
      7 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides Claude Code with a repository symbol graph via tree-sitter, enabling instant symbol lookup, file skeletons, call-site analysis, and persistent notes, reducing token usage by reading signatures instead of whole files.
      12
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to efficiently analyze codebases by extracting AST skeletons, reducing token usage while preserving type contracts and interfaces.
      2 npm
      1
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Persistent daemon that compresses codebases via AST body folding before indexing them for AI coding assistants like Claude Code and Cursor 57-89% token reduction with sub-millisecond queries, verified on Django, Spring, and Next.js.
      12
      4
      -

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: edit_file modifies content, file_status shows tracking info, forget_file removes tracking, peek_file summarizes without activation, read_file reads and activates, and write_file creates/writes and activates. The descriptions clearly differentiate their functions, preventing misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., edit_file, read_file, write_file) with no deviations in style or casing. This uniformity makes the tool set predictable and easy to navigate for an agent.

    Tool Count5/5

    With 6 tools, the server is well-scoped for file compaction and management, covering essential operations like reading, writing, editing, tracking, and summarizing files. Each tool serves a necessary function without redundancy or bloat.

    Completeness4/5

    The tool set provides strong coverage for file compaction workflows, including CRUD-like operations (read, write, edit, forget) and status/summary features. A minor gap is the lack of a tool for batch operations or handling multiple files at once, but agents can work around this by iterating through individual tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues