LLMScribe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ALLOWED_ROOTS | No | Directories (separated by `:` on POSIX, `;` on Windows) the tools may read. Default: all paths. | all paths |
| MCP_ALLOW_LOCAL_PATHS | No | `0` disables local path access entirely. Default: enabled. | enabled |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_mapB | Directory tree and the list of supported text files, without file contents. Respects default ignores and .gitignore files. Symlinks are not followed. |
| project_overviewB | Directory tree plus the contents of supported text files. Output is capped at 400,000 characters of file content; when capped, the result says so and lists the omitted files. |
| searchA | Substring search over file names and file contents. Results are ordered by path then line number and limited to 1,000 matches. Binary and oversized files are skipped. This is plain text matching, not semantic search. |
| readA | Read one text file. Paths cannot leave the root; binary and oversized files are rejected. |
| read_manyB | Read several text files in one call. A bad path yields an error entry; other files are still read. |
| project_dependenciesB | Imports of one file (local, standard-library, external, unresolved) and the files that import it. Supports Python, JavaScript/TypeScript, Java, Go, Rust and C/C++. |
| project_diffA | Git status and unified diff of the working tree (vs HEAD, vs 'commit', or staged only). |
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 are cleanly separated by purpose: search vs read vs read_many vs project_diff are unambiguous. The one soft overlap is project_map vs project_overview, which both return a directory tree, though the descriptions make the contents-vs-no-contents distinction explicit. project_dependencies is clearly distinct in output shape.
All names are snake_case, but the convention is applied unevenly: some carry a project_ prefix (project_map, project_overview, project_dependencies, project_diff) while the core file operations are bare verbs (search, read, read_many). Readable, but an agent can't infer the prefix rule predictably.
Seven tools is well within the ideal range and each one earns its place: three discovery tools, two read tools, a dependency tool, and a diff tool. No redundant or filler entries.
The read-only exploration lifecycle is largely covered: map, bulk overview, search, single/bulk read, dependency graph, and git diff. Minor gaps remain, such as no line-range or offset read for large files and no pattern/glob filtering when listing files, all of which agents can work around with search.