Skip to main content
Glama
eduardoddddddd

DesktopCommanderPy

by eduardoddddddd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to DesktopCommanderPy

No user-submitted related servers found.

    Related Servers

    • Claude Local Bridge

      suhteevah
      A
      license
      Not graded
      quality
      D
      maintenance
      A secure MCP server that allows Claude to read and write local files on your machine with explicit approval gating for each access.
      MIT

    • mcp-common-server

      tamilts124
      F
      license
      Not graded
      quality
      B
      maintenance
      Zero-dependency MCP server that provides AI models with secure read/write/exec access to local files and directories over HTTP and SSE, designed to be tunneled via ngrok for integration with Claude Web.
      -

    • NotiCode

      Antropov31
      A
      license
      A
      quality
      B
      maintenance
      Runs as an MCP server providing file system operations, shell execution, and system information tools, allowing Claude or any MCP client to edit files and control the machine.
      2
      7
      MIT

    • computer-use-mcp

      domdomegg
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that enables Claude to control your computer, similar to Anthropic's computer use but easy to set up locally.
      460 npm
      376
      MIT

    • claude-work-mcp

      blaspinto5
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that connects Claude Code to your work environment through auditable tools for file operations, API calls, and command execution, with safety gates and configuration.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools have distinct purposes, e.g., file vs. process vs. database. Minor overlap between kill_process and force_terminate, and execute_command vs. execute_command_streaming, but descriptions clarify the differences.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., create_directory, execute_command, hana_describe_table). No mixing of styles or unexpected variations.

    Tool Count3/5

    With 28 tools, the count is high but still manageable. It spans file operations, process management, SAP HANA, and config, which may justify the count, but it feels slightly heavy for a single MCP server.

    Completeness2/5

    The file tools cover create, read, write, edit, move, list, search, but notably lack delete and copy operations, which are obvious gaps for a desktop commander. Process and HANA tools are more complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources