MCP Files
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port (when TRANSPORT=http) | 4657 |
| DEBUG | No | Enable debug mode and utils_debug tool | false |
| TRANSPORT | No | Transport mode: stdio or http | stdio |
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 | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_symbolA | Find and extract symbol block by name from files, supports a lot of file formats (like TS, JS, GraphQL, CSS and most that use braces for blocks). Uses streaming with concurrency control for better performance |
| insert_textA | Insert or replace text at precise line ranges in files
|
| os_notificationB | Send OS notifications using native notification systems. |
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 3 tools
Each tool has a clearly distinct purpose: insert_text handles line-based file editing, os_notification sends OS notifications, and read_symbol extracts symbol blocks from files. There is no overlap in functionality, making tool selection straightforward for an agent.
The naming follows a consistent verb_noun pattern (insert_text, read_symbol, os_notification), which is predictable and readable. The slight deviation is that os_notification uses an underscore but starts with 'os' as a prefix, which is still coherent with the overall style.
With only 3 tools, the server feels thin for a general-purpose 'MCP Files' domain, as it lacks basic file operations like reading, writing, or deleting entire files. However, the tools are specialized and focused, so it's borderline but not severely mismatched.
The tool set is significantly incomplete for a files-oriented server, missing core operations such as reading file contents, writing files, deleting files, or listing directories. While the provided tools are useful for specific tasks, agents will face gaps in handling common file workflows.