IMALI Commander
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMALI_HOME | No | Change the config folder. | |
| IMALI_HOST | No | Host to listen on for HTTP transport. | 127.0.0.1 |
| IMALI_PORT | No | Port to listen on for HTTP transport. | 8787 |
| IMALI_AUDIT_LOG | No | Audit log path; set to off to disable auditing. | ~/.imali-commander/logs/audit.log |
| IMALI_MCP_TOKEN | No | Plaintext MCP token (32+ characters); overrides the token hash. | |
| IMALI_READ_ONLY | No | Enable read-only mode, removing write_file, upload_file and create_directory. | false |
| IMALI_TRANSPORT | No | Transport mode; use http for HTTP. | stdio |
| IMALI_WORKSPACE | No | Workspace folder the server is scoped to. | ~/imali-workspace |
| IMALI_LICENSE_KEY | No | Pro license key; activates on first start, useful for containers. | |
| IMALI_ALLOW_REMOTE | No | Allow remote access; only use behind a reverse proxy with HTTPS. | false |
| IMALI_MAX_SESSIONS | No | Maximum number of HTTP sessions. | 16 |
| IMALI_MCP_TOKEN_SHA256 | No | SHA-256 hash of the MCP token; set by init. | |
| IMALI_TRUST_REVERSE_PROXY | No | Trust proxy headers when running behind a reverse proxy. | 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| device_infoC | Describe connected local computer and workspace |
| list_filesC | List files within approved workspace |
| read_fileB | Read UTF-8 file in workspace (up to 1 MB) |
| write_fileC | Create or replace UTF-8 file in workspace |
| download_fileA | Read a small workspace file as base64 for transfer to an MCP client (max 5 MB) |
| upload_fileB | Write base64-encoded file into approved workspace (max 5 MB) |
| create_directoryC | Create a directory within approved workspace |
| file_infoB | Show metadata for a file or directory in the workspace |
| search_filesC | Search filenames recursively within the workspace |
| run_workspace_commandB | Run a limited read-only command in the workspace; no shell or arbitrary programs |
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 10 tools
Each tool targets a distinct action: device info, listing, reading, writing, base64 transfer, directory creation, metadata, filename search, and command execution. read_file and download_file overlap slightly, but the descriptions clearly distinguish UTF-8 content from base64 transfer.
Most names follow a consistent verb_noun snake_case pattern (list_files, read_file, write_file, download_file, upload_file, create_directory, search_files). The noun-only names device_info and file_info are minor deviations but remain readable and domain-consistent.
Ten tools is a well-scoped set covering read, write, transfer, metadata, search, and command operations. No tool appears redundant.
Core file operations are covered, but there is no delete_file or delete_directory, no move/rename or copy, and no append/update-in-place operation (write_file replaces). Agents needing cleanup or reorganization hit dead ends.