Skip to main content
Glama

Related Servers

Alternatives to TRAECNclaw MCP

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients on Windows 10/11 to control an interactive desktop through screenshots, mouse and keyboard actions, window management, UI Automation, clipboard access, and multi-display switching. Supports batched actions, application access controls, and visual or text-based desktop interaction.
      377 npm
      1
      MIT
    • 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to automate live browser sessions by having an LLM plan one outcome at a time while a hosted decision model picks elements, actions, values, and completion status. It exposes tools for navigation, direct actions, page reading/snapshots, checks/choices, screenshots, and calling WebMCP tools registered by pages.
      889 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 20 tools

    Disambiguation4/5

    The tool set is largely cleanly partitioned: tasks, conversations, settings, models/modes, workspace, and interaction handling each have their own verbs. The only genuinely fuzzy pair is cancel_task vs stop_generation, but the description explicitly tells the agent to prefer cancel_task when a task ID exists, and the settings trio (toggle/option/text) is distinguished by control type. A few tools (list_settings vs list_setting_options vs list_setting_sections) are close cousins but the descriptions establish a clear required ordering.

    Naming Consistency5/5

    Every tool uses the uniform traecn_<verb>_<noun> snake_case pattern (list_, select_, set_, create_, delete_, get_, cancel_, stop_, send_, open_, answer_, decide_). Verbs are used semantically consistently: list_ for read-only discovery, select_ for choosing from a listed set, set_ for applying a value. No camelCase or style mixing anywhere.

    Tool Count4/5

    Twenty tools is on the heavy side, but the server spans several distinct sub-domains (task lifecycle, conversation lifecycle, settings discovery/mutation, model/mode selection, approvals, workspace), so most tools earn their place. It is borderline rather than bloated, and consolidation of the four settings tools would make it tighter.

    Completeness4/5

    Coverage is strong across most lifecycles: tasks (send/get/cancel), conversations (list/select/create/delete), settings (sections/list/options/set/select), models and mode, workspace opening, and interactive prompts (answer_question, decide_approval). Minor gaps remain — there is no list_tasks to enumerate tracked work, no conversation rename, and no workspace listing/current-workspace read — but agents can work around these using the returned taskId.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues