
civyk-official/civyk-winwright
Browser automationЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
Playwright-style MCP server for Windows desktop, system, and browser automation. 52 tools for WPF, WinForms, Win32, Chrome/Edge via Model Context Protocol.
Обзор
Windows automation server for the Model Context Protocol. 52 consolidated tools for desktop (WPF, WinForms, Win32), browser (Chrome/Edge via CDP), and system management — accessible to AI agents over MCP, . You write test cases in plain English. The AI agent uses WinWright's MCP tools to discover UI controls, perform actions, and record everything as a portable JSON script. Once recorded, scripts run deterministically with winwright run — no AI agent, no LLM calls, no token costs. Results are the same every time. If the UI layout changes, WinWright can broken selectors automatically (winwright heal). For larger UI redesigns, ask the AI agent to update the script — still faster than rewriting tests from scratch.
README
Показан фрагмент оригинального README. Открыть оригинал.
WinWright
Windows automation server for the Model Context Protocol.
52 consolidated tools for desktop (WPF, WinForms, Win32), browser (Chrome/Edge via CDP),
and system management — accessible to AI agents over MCP, or driven directly from the
command line (winwright call …) when MCP is blocked.
Describe tests in plain English — the AI agent does the rest
You write test cases in plain English. The AI agent uses WinWright’s MCP tools to discover UI controls, perform actions, and record everything as a portable JSON script.
Replay recorded scripts — no AI agent needed
Once recorded, scripts run deterministically with winwright run — no AI agent,
no LLM calls, no token costs. Results are the same every time.
If the UI layout changes, WinWright can self-heal broken selectors automatically
(winwright heal). For larger UI redesigns, ask the AI agent to update the script —
still faster than rewriting tests from scratch.
Why this matters:
- Save AI costs — the agent records once, scripts replay for free
- Deterministic results — every run produces identical, reproducible outcomes
- Easy maintenance — self-healing selectors and AI-assisted script repair
Contents
- Quick Start
- Install
- MCP Client Configuration
- CLI Mode (when MCP is blocked)
- Use Cases
- Tools
- Configuration
- Who Is This For
- How It Compares
- Support
- License
Quick Start
Install, configure your MCP client, then ask the agent to do something:
“Launch Notepad, type ‘Hello from WinWright’, then read back what you typed.”
The agent calls WinWright tools and returns results:
ww_launch → { "processId": 12840, "mainWindowTitle": "Untitled - Notepad" }
ww_type → { "success": true }
ww_get_value → { "value": "Hello from WinWright" }
Every tool returns structured JSON. The agent decides which tools to call and in what order — you describe the goal in plain language.
Install
Download from GitHub Releases:
| Asset | Architecture |
|---|---|
winwright-*-win-x64.zip |
Intel/AMD 64-bit |
winwright-*-win-arm64.zip |
ARM64 (Surface Pro, etc.) |
Установка
This server does not publish a one-line install command.
Open the repository installation guide Новичок в MCP? Начните с руководства на mcpskill.org →Конфигурация
{
"mcpServers": {
"winwright": {
"command": "C:/path/to/Civyk.WinWright.Mcp.exe",
"args": ["mcp"]
}
}
}