Large File MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL | No | Cache TTL in milliseconds (default: 5 minutes) | 300000 |
| CACHE_SIZE | No | Cache size in bytes (default: 100MB) | 104857600 |
| CHUNK_SIZE | No | Default lines per chunk | 500 |
| CACHE_ENABLED | No | Enable/disable caching | true |
| MAX_FILE_SIZE | No | Maximum file size in bytes (default: 10GB) | 10737418240 |
| OVERLAP_LINES | No | Overlap between chunks | 10 |
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_large_file_chunkA | Read a specific chunk of a large file with intelligent chunking based on file type. Automatically determines optimal chunk size. |
| search_in_large_fileA | Search for a pattern in a large file with context lines. Supports regex and case-sensitive search. |
| get_file_structureB | Analyze file structure and get comprehensive metadata including line statistics, recommended chunk size, and samples from start and end. |
| navigate_to_lineA | Jump to a specific line in a large file with surrounding context lines. Highlights the target line. |
| get_file_summaryA | Get comprehensive statistical summary of a file including line stats, character stats, and word count. |
| stream_large_fileC | Stream a large file in chunks. Returns multiple chunks for processing very large files efficiently. |
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
Most tools have clearly distinct purposes (navigate, search, stream, read chunk). However, get_file_structure and get_file_summary both provide file statistics, creating slight ambiguity about which to use for metadata needs.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_file_structure, navigate_to_line). The naming is predictable and clear across all six tools.
Six tools cover the core capabilities for reading and analyzing large files (structure, summary, navigation, chunking, searching, streaming). The count is well-scoped for the domain.
The tool set provides comprehensive read-only operations: structural metadata, statistical summary, targeted line access, chunked reading, pattern searching, and streaming. No obvious gaps for the declared purpose.