{"id":"civyk-official-civyk-winwright","name":"civyk-winwright","af_score":59.0,"security_score":40.5,"reliability_score":23.8,"what_it_does":"WinWright is a Windows-only automation server that exposes ~59 tool endpoints to AI agents via Model Context Protocol (MCP) for controlling and inspecting Windows desktop applications (WPF/WinForms/Win32 via UI Automation) and Chrome/Edge (via CDP). It supports recording actions into portable JSON scripts for deterministic replay (winwright run) and can attempt self-healing of broken selectors (winwright heal).","best_when":"You need an MCP-compatible tool server that can drive the Windows desktop UI (plus optional Chrome/Edge via CDP) and you want deterministic replay via recorded scripts.","avoid_when":"You cannot run Windows 10/11, or you need primarily web-only testing, or you require strict, documented enterprise-grade security (authn/z, TLS, and operational guarantees) beyond a local tool-server model.","last_evaluated":"2026-03-30T15:22:36.648193+00:00","has_mcp":true,"has_api":false,"auth_methods":["Local/stdio MCP server (no mention of authentication in README)","HTTP MCP server (README does not document authentication; only claims about remote administration security controls)"],"has_free_tier":false,"known_gotchas":["Tool server is Windows-only and relies on UIA/desktop state; agent actions may fail if the UI is not ready or focus is different.","For HTTP MCP mode, ensure you control network exposure; README examples use localhost.","Statefulness: launching apps and interacting with UIs is not naturally idempotent—retries may cause duplicated actions unless the caller uses appropriate guards."],"error_quality":0.0}