
Playwright 风格的 MCP 服务器,适用于 Windows 桌面、系统和浏览器自动化。52 个支持 WPF、WinForms、Win32、Chrome/Edge 通过模型上下文协议的工具。
概览
用于模型上下文协议的Windows自动化服务器。52个整合工具,适用于桌面(WPF、WinForms、Win32)、浏览器(通过CDP的Chrome/Edge)和系统管理——通过MCP对AI代理开放。 你用通俗易懂的英语写测试用例。AI代理使用WinWright的MCP工具来发现UI控件、执行操作,并以可移植的JSON脚本形式记录所有内容。 一旦记录,脚本会以确定性方式运行,并以Winwright运行——没有AI代理,没有LLM调用,没有代币成本。每次结果都是一样的。 如果界面布局发生变化,WinWright 可以自动破坏选择器(Winwright 修复)。对于较大规模的 UI 重设计,可以让 AI 代理更新脚本——这仍然比从头重写测试快。
概述(AI 翻译)
用于模型上下文协议的Windows自动化服务器。
52个整合工具,适用于桌面(WPF、WinForms、Win32)、浏览器(通过CDP的Chrome/Edge),
以及系统管理——AI代理可通过MCP访问,或直接从中驱动
当MCP被阻塞时,命令行(winwright call …)。
用通俗易懂的语言描述测试——AI代理完成剩下的
你用通俗易懂的英语写测试用例。AI代理使用WinWright的MCP工具 发现界面控件,执行操作,并以可移植的JSON脚本记录所有内容。
重播录制脚本——无需AI代理
一旦记录,脚本以确定性方式运行,使用 winwright run —— 无 AI 代理,
没有LLM调用,也没有代币成本。每次结果都是一样的。
如果界面布局改变,WinWright 可以自我修复损坏的选择器
(winwright heal)。对于更大规模的UI重新设计,请让AI代理更新脚本——
这仍然比从头重写测试快。
为什么这很重要:
- 节省AI成本 — 代理记录一次,脚本免费重播
- 确定性结果——每次运行都产生相同且可重复的结果
- 维护简便 — 自我修复选择器和AI辅助脚本修复
本页由 AI 翻译,技术细节请以原文为准。
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 新手?先看 mcpskill.org 教程 →配置
{
"mcpServers": {
"winwright": {
"command": "C:/path/to/Civyk.WinWright.Mcp.exe",
"args": ["mcp"]
}
}
}