local-mcp-simple-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIMPLE_MCP_SOURCE_ROOT | Yes | An absolute path to the directory this server is allowed to read from. Configured via SIMPLE_MCP_SOURCE_ROOT. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_source_fileA | Reads one UTF-8 text file from the server's configured source root and returns its relative path and complete text. Files over 64 KiB are rejected, not truncated. The caller cannot choose or change the root; only a path relative to it. |
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 1 tool
Only one tool exists, so there is no possibility of confusion or overlap. Every call is clearly directed to the single available operation.
The tool name 'read_source_file' follows a clear verb_noun pattern, which is consistent even though it is the only tool. The naming is descriptive and predictable.
A single tool feels thin for a server, but the purpose is explicitly simple (reading one file at a time), so it borders on acceptable. It would benefit from at least one companion tool like list_source_files.
The server only supports reading one file and offers no listing, writing, or directory traversal capabilities. Agents must know exact relative paths in advance, making workflows fragile and incomplete.