TRAECNclaw MCP
Related Servers
Alternatives to TRAECNclaw MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides desktop automation capabilities (e.g., click, browser snapshot) as MCP tools for DSH agents, enabling computer use via natural language.234 npm5MIT
- FlicenseNot gradedqualityDmaintenanceEnables automation of native Windows desktop applications through screen capture, mouse/keyboard control, and waiting for UI changes, exposing them as MCP tools.1-
- AlicenseNot gradedqualityBmaintenanceEnables 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 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables models to remotely control computers over an MCP link, running commands, managing files, automating desktops and browsers, transferring data, and coordinating durable tasks across sessions.626 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmMIT
TDQS
Scored across 20 tools
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.
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.
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.
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.