MCP File Compaction
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileA | Read a file and mark it as the active file. When you switch to a different file, the previous file is automatically summarized to just its public interface, reducing context size. Supported languages for summarization: .rs, .py, .ts, .tsx, .js, .jsx, .php, .cs, .gd For unsupported file types, returns full contents without tracking (same as standard file read). |
| peek_fileA | Get a summary of a file's public interface without changing the active file. Useful for checking APIs of files you've already worked on. Returns:
|
| edit_fileA | Edit a file by replacing a specific string. The file becomes (or remains) the active file. The old_string must:
After editing, the file's cached summary is updated. |
| write_fileA | Write content to a file, creating it if it doesn't exist. The file becomes the active file. Creates parent directories if needed. |
| file_statusB | Show the status of all tracked files including:
|
| forget_fileB | Remove a file from tracking. Useful for cleanup or when you no longer need a file's interface in context. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.