emperor-folder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUST_LOG | No | Log level; logs go to stderr. | info |
| FOLDER_WRITABLE | No | true, 1, yes or on offers write, edit and move; unset or false keeps the server read-only. | false |
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 |
|---|---|
| listA | List files and directories in a folder. Skips hidden and .gitignored entries. Optional glob filter; recursive for subfolders. |
| readA | Read a text file, optionally only lines start_line..end_line (1-based, inclusive). Small PNG, JPEG, GIF and WebP images come back as images; other binary files are reported, not returned. |
| searchA | Search text files for a regular expression; returns path, line number and line for each match. Optional start path, glob filter, ignore_case. |
| statA | Describe a path: kind (file, dir, symlink), size, modified time, line count for text files, image type for images. |
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 4 tools
Each tool has a clearly distinct purpose: list enumerates directory contents, read returns file contents, search finds regex matches, and stat describes metadata. There is little risk of confusing these operations, even though list and search can both traverse folders.
All four tools use short, lowercase verb-style names with a consistent convention. The pattern is predictable and readable throughout the set.
Four tools are well-scoped for a folder/filesystem inspection server. Each tool covers a distinct core operation without unnecessary bloat.
The surface covers read-only filesystem workflows well: listing, reading, searching, and metadata inspection. If write operations such as create, delete, or move are expected for a folder server, those are missing, but the read-only scope appears intentional.