Skip to main content
Glama
Luckycat133

TRAECNclaw MCP

by Luckycat133
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to TRAECNclaw MCP

No user-submitted related servers found.

    Related Servers

    • atomic-computer-mcp

      Dawdler-G
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables automation of native Windows desktop applications through screen capture, mouse/keyboard control, and waiting for UI changes, exposing them as MCP tools.
      1
      -

    • SoftAuto

      guangfubill-crypto
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to perform deterministic Windows desktop and browser automation through MCP, using pre-validated UI Automation and DOM locators for fast, stable execution of ERP and business workflows.
      2
      MIT

    • Desktop-MCP

      talkwitharnav-web
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables supervised, visible control of a Windows desktop from an MCP client, providing real mouse and keyboard input, screenshots, local safety controls, and a teaching mode for guidance without injection.
      MIT

    • winagent

      ZYYDI1959
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI platforms to see the screen and operate any desktop software through real mouse clicks, text input, key presses, and scripted scenario execution.
      MIT
    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

    A4.4/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., cancel_task vs stop_generation are clearly separated by scope: gateway task vs visible generation). No two tools overlap in purpose, and descriptions reinforce unique use cases.

    Naming Consistency5/5

    All tools follow a strict `traecn_` prefix with a consistent verb_noun pattern (get_task, list_models, select_mode, set_setting_toggle, create_conversation). No mixed conventions or vague verbs.

    Tool Count5/5

    20 tools cover a broad but well-defined domain: task lifecycle, workspace/model/mode control, settings management, conversation CRUD, and exceptional interaction handling. Each tool earns its place, and the count is appropriate for the server's comprehensive scope.

    Completeness5/5

    The surface covers the full lifecycle: task submission, retrieval, cancel, and emergency stop; complete CRUD for conversations; full discovery and mutation for settings; model/mode selection; and exceptional handling (questions, approvals). No obvious gaps that would leave agents dead-ended.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources