MCP Local File Reader
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ROOT_PATH | No | Root directory for file access (defaults to current working directory) |
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 |
|---|---|
| list_directoryB | List contents of a directory. Returns file and directory information including names, types, sizes, and modification dates. |
| read_fileA | Read file content with automatic format detection. Supports text files, PDF, Excel, Word, PowerPoint, and CSV with automatic encoding detection (Shift-JIS/UTF-8). |
| get_file_infoB | Get metadata about a file or directory including size, type, and modification date. |
| search_contentA | Search for text pattern in files (grep-like functionality). Returns list of unique file paths containing the pattern. Recursively searches all subdirectories by default. Automatically skips node_modules, .git, dist, build directories and binary files for performance. |
| find_filesA | Find files by name pattern. Returns list of matching file paths. Recursively searches all subdirectories by default. |
| list_excel_sheetsB | List all sheet names in an Excel file (.xlsx or .xls). |
| read_excel_sheetB | Read a specific sheet from an Excel file. Returns data as JSON. |
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 7 tools
Most tools have distinct purposes, but there is some overlap between find_files and search_content, as both involve searching files, which could cause minor confusion. However, their descriptions clarify that find_files searches by name pattern while search_content searches by text pattern, helping to differentiate them.
All tool names follow a consistent verb_noun pattern (e.g., find_files, get_file_info, list_directory), with no deviations in style or convention. This predictability makes the tool set easy to navigate and understand.
With 7 tools, the count is well-scoped for a local file reader server, covering essential operations like listing, reading, and searching files. Each tool serves a clear purpose without redundancy, making the set appropriately sized for the domain.
The tool set covers core file operations including listing, reading, and searching, with good support for various file formats. A minor gap is the lack of write or update operations, but this is reasonable for a read-focused server, and agents can still perform common workflows without dead ends.