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:

MCP Client Configuration

Claude Code / VSCode (stdio)

{
  "servers": {
    "winwright": {
      "type": "stdio",
      "command": "C:/path/to/Civyk.WinWright.Mcp.exe",
      "args": ["mcp"]
    }
  }
}

Claude Code / VSCode (HTTP)

Start the server first: Civyk.WinWright.Mcp.exe serve --port 8765

{
  "servers": {
    "winwright": {
      "type": "http",
      "url": "http://localhost:8765/mcp"
    }
  }
}

Claude Desktop

{
  "mcpServers": {
    "winwright": {
      "command": "C:/path/to/Civyk.WinWright.Mcp.exe",
      "args": ["mcp"]
    }
  }
}

CLI Mode (when MCP is blocked)

Many corporate environments block MCP. WinWright can be driven entirely from the command line instead — the same tools, the same automation, with no MCP client between the agent and the tool. A background daemon (a loopback serve instance) owns the live sessions, so the appId returned by ww_launch stays valid across separate commands.

winwright too

... [View full README on GitHub](https://github.com/civyk-official/civyk-winwright#readme)