Skip to main content
Glama
wonderwhy-er

Claude Desktop Commander MCP

by wonderwhy-er

Related Servers

Alternatives to Claude Desktop Commander MCP

  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to interact with B\&R Automation Studio projects by building code, running ARsim simulators, and reading or writing OPC UA variables. It facilitates industrial automation development and real-time variable integration through natural language commands.
    14
    MIT

Related Servers

  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables Claude Desktop or other MCP clients to execute shell commands, read/write files, and list directories on the local machine. Includes basic safety guardrails to block obviously destructive operations.
    -
  • A
    license
    A
    quality
    D
    maintenance
    A server that lets Claude desktop app execute terminal commands on your computer and edit files through Model Context Protocol, featuring command execution, process management, and advanced file operations.
    19
    207,385 npm
    6
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Exposes an interactive terminal over MCP, enabling remote shell command execution, file operations, and directory management via ChatGPT or Claude Desktop.
    2
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables voice assistants to start, monitor, message, and approve local Claude Code sessions on your computer, including sessions already open in a terminal. It exposes session management, recaps, approvals, and history search as MCP tools.
    2
    GPL 3.0

TDQS

A3.6/5.0

Scored across 25 tools

Disambiguation4/5

Most tools target a distinct resource+action, but there are a couple of overlapping pairs: force_terminate vs kill_process (both terminate processes) and list_sessions vs list_processes (both enumerate running things). The search group (start/stop/list/get_more) is well-differentiated. Overall mostly clean, with minor boundary confusion.

Naming Consistency5/5

Names are uniformly snake_case with a clear verb_noun pattern (read_file, write_file, create_directory, list_directory, start_process, kill_process, get_config, start_search). Even the longer names like give_feedback_to_desktop_commander and get_more_search_results follow the same convention. No mixed casing or style drift.

Tool Count4/5

25 tools is on the heavy side, but the server spans several genuinely distinct subsystems (filesystem, terminal processes, search, config, PDF/DOCX/Excel, telemetry), so most tools earn their place. A few telemetry/feedback tools (get_usage_stats, give_feedback_to_desktop_commander) feel marginal and could be trimmed.

Completeness3/5

Filesystem coverage includes read, write, create_directory, list, move, edit, and info, but there is no delete_file or delete_directory tool, leaving a notable gap in CRUD/lifecycle coverage. Deletion can only be achieved indirectly via start_process, which is a workaround rather than a first-class operation. Process and search lifecycles are otherwise well covered.

Maintenance

ActivityActive
ResponsivenessWithin a week