Skip to main content
Glama
jordelmir

Elysium Desktop Commander

by jordelmir

Related Servers

Alternatives to Elysium Desktop Commander

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables local macOS automation via the Model Context Protocol, allowing file operations, system monitoring, shell commands, clipboard access, and screenshots with configurable security restrictions.
      14
      MIT

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues