Skip to main content
Glama
Claude Desktop Commander MCP

Claude Desktop Commander MCP

by StrawHatAI

Related Servers

Alternatives to Claude Desktop Commander MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides Claude Desktop with direct access to your local file system for development tasks, enabling file operations (read, write, edit), directory browsing, command execution, and codebase search within a configured projects directory.
      6
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to perform file operations, retrieve system information, run calculations, and generate timestamps on the local system.
      -
    • 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
      C
      quality
      A
      maintenance
      Enables Claude Desktop to control a local host machine through shell, file, git, network, Docker, package, and system monitoring tools, with approval-gated destructive operations.
      146
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Desktop and Claude Code to list, search, and read files, run one terminal command, query SQLite, and manage named scheduled tasks without calling the Claude API.
      MIT

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no significant overlap. For example, read_file and read_multiple_files are clearly differentiated by single vs. batch operations, while edit_block and write_file are distinguished by surgical vs. complete replacement use cases. The command blocking tools (block_command, unblock_command, list_blocked_commands) form a coherent subsystem without confusion.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with perfect consistency throughout. The naming convention is uniformly descriptive and predictable, making it easy to understand each tool's function at a glance. Examples include list_directory, create_directory, move_file, and search_files.

    Tool Count4/5

    With 19 tools, the count is slightly high but reasonable for a desktop command and file management server. The tools cover multiple domains (file operations, process management, terminal sessions, command blocking), and most tools earn their place. A slight reduction might improve focus, but the scope justifies the current count.

    Completeness5/5

    The tool surface provides comprehensive coverage for desktop command and file management operations. It includes full CRUD for files (create_directory, read_file, edit_block/write_file, move_file), process lifecycle management (list_processes, kill_process), terminal session control (execute_command, list_sessions, read_output, force_terminate), and command security (block/unblock). No obvious gaps exist for the server's stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing