file-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FILE_MCP_ALLOWED_ROOTS | No | Allowed root directories for file access. Separate multiple with semicolons. Set to '*' to disable restrictions. | F:\ |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apply_text_spansC | Apply multiple non-overlapping normalized-text span edits using 0-based offsets. |
| write_full_textB | Write an entire text file with explicit style controls and optional base-hash protection. |
| apply_text_editsB | Apply multiple non-overlapping line-range edits in a single atomic write. |
| replace_literalC | Replace literal text only when the exact expected occurrence count matches. |
| replace_regexC | Replace regex matches only when the exact expected occurrence count matches. |
| replace_blockA | Replace a marker-delimited block with base-hash protection and style preservation. |
| begin_write_sessionC | Start a chunked write session for large generated files. |
| append_write_chunkC | Append a text chunk to an open write session. |
| commit_write_sessionB | Commit a chunked write session via a single atomic file replacement. |
| abort_write_sessionB | Abort a chunked write session without writing anything. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server_config |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: session management, various replace methods, and full file writing. No two tools appear to do the same thing, and descriptions clarify the differences.
All tool names follow a consistent verb_noun snake_case pattern (e.g., abort_write_session, replace_literal), making them predictable and easy to interpret.
10 tools is well within the ideal range. Each tool addresses a specific file editing operation without being excessive or insufficient.
The tool set lacks basic file operations like reading, deleting, or listing files. While editing and writing are covered, the absence of read functionality creates a significant gap for typical file management workflows.