Elysium Desktop Commander
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ELYSIUM_AUDIT_LOG | No | Set to opt into metadata-only audit records. | |
| ELYSIUM_REMOTE_TOKEN | No | Unique random bearer token of at least 32 bytes, required when starting the optional loopback Streamable HTTP endpoint. | |
| ELYSIUM_ALLOWED_ROOTS | No | Platform-separated list of explicitly authorized roots. Defaults to the current working directory. |
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 |
|---|---|
| get_healthA | Return agent health, active policy, platform support and session count. |
| list_allowed_rootsA | List the filesystem roots explicitly authorized for reads and process working directories. |
| list_directoryC | List a bounded directory without following symlink entries. |
| read_fileB | Read a UTF-8 text file under an authorized root with a strict byte limit. |
| get_file_metadataC | Return non-content metadata for an authorized path. |
| search_filesC | Search file names beneath an authorized root with bounded depth and result count. |
| run_commandA | Run a short, read-only allowlisted command without a shell. No arbitrary command or shell syntax is accepted. |
| start_processC | Start an allowlisted bounded process session. The command still runs with this user account privileges. |
| list_processesA | List process session metadata created by this agent without including process output. |
| read_process_outputB | Read a bounded page of output and status for an agent process session. |
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
Most tools have clearly distinct purposes: filesystem reads, metadata, search, process sessions, and health/roots are well separated. The only notable overlap is run_command versus start_process, though their descriptions distinguish short read-only commands from bounded process sessions.
All tools use a consistent snake_case verb_noun pattern such as get_health, list_directory, read_file, and start_process. There are no mixed conventions or vague standalone verbs.
Ten tools is well-scoped for a desktop commander focused on authorized filesystem reads and bounded process control. Each tool maps to a distinct operation without excessive surface area.
The read-only filesystem and process inspection surface is fairly coherent, but there are notable lifecycle gaps: no file write/edit/delete operations and no process stop/kill operation. These gaps may be intentional for a security-restricted server, but they are still significant for a general desktop commander.