Elysium Desktop Commander
Related Servers
Alternatives to Elysium Desktop Commander
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to explicitly approved local and remote filesystems, including inspecting Git repositories and querying SQLite and DuckDB databases, with root administration kept separate from MCP.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to run files, processes, shell sessions, browser automation, and native macOS UI actions under explicit workspace permissions and auditable controls.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables read-only, allowlisted filesystem and Git inspection of explicitly configured local repositories through MCP, with bounded reads and no arbitrary path or write access.8 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables local project file access, editing, command execution, recoverable long-running jobs, Apple MPS checks, and macOS UI automation through MCP.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP agents to control macOS natively with shell, PTY, background Chrome automation, and Accessibility-based desktop control.4MIT
- AlicenseAqualityBmaintenanceEnables local macOS automation via the Model Context Protocol, allowing file operations, system monitoring, shell commands, clipboard access, and screenshots with configurable security restrictions.14MIT
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.