Every listicle for UI automation tools still ships a GUI. Terminator ships 35 MCP tools.

The top eight search results for "ui automation tools" in 2026 all rank the same names: Selenium, Playwright, Cypress, TestComplete, Ranorex, Katalon, Applitools, UiPath. Every one of them was built for a human to drive through an IDE or a recorder. The category grew a second branch when MCP shipped: UI automation tools that are not apps at all, but a bundle of callable tools the AI coding assistant holds in context. Terminator has 35 of them in one binary.

35 MCP toolsClaude CodeCursorVS CodeWindsurfMIT
M
Matthew Diakonov
10 min read
4.9from developers shipping AI-driven desktop workflows
35 MCP tools, verifiable: grep -c '#[tool(' server.rs
One install line for Claude Code, Cursor, VS Code, Windsurf
Covers every Windows desktop app + Chromium via extension
Fallback run_ai_agent wraps Gemini 2.5 Computer Use

What the top of the SERP keeps missing

I pulled the top eight ranking pages for the query "ui automation tools" in April 2026. Virtuoso, CPO Club, UI Things, TestMu, T-Plan, SoftwareTestingHelp, Ranorex, Functionize. Every article is a listicle. The same twenty or so names rotate through: Selenium, Playwright, Cypress, Appium, Katalon, TestComplete, Ranorex, Testim, Mabl, ACCELQ, LambdaTest, BrowserStack, Applitools, Robot Framework, TestSprite. Not one of them mentions the Model Context Protocol. Not one mentions Claude Code, Cursor, or any MCP client. Not one frames UI automation as developer infrastructure for an AI assistant, which in 2026 is where most of the actual automation work is flowing.

The gap is not subtle. It is the entire premise. A UI automation tool in 2026 is a vocabulary the agent speaks, not a GUI a human clicks. Terminator is built for the first reading of that sentence. Every other entry on the SERP is built for the second.

The anchor fact: 35 MCP tools in one file

The claim is verifiable from the repo. Clone github.com/mediar-ai/terminator, run grep -c "#[tool(" crates/terminator-mcp-agent/src/server.rs, and you get 35. Each annotation decorates a function that becomes an MCP tool exposed to the agent. Below is the full list grouped by what the agent uses it for.

crates/terminator-mcp-agent/src/server.rs

Compare to Playwright MCP, which exposes roughly 15 tools and is browser-only. Compare to Puppeteer's community MCP wrappers, same scope. Compare to the rest of the listicle, which has zero MCP surface at all.

How the agent actually reaches the OS

One stdio connection between the MCP client and the Terminator binary. The binary fans out into three backends: Windows UI Automation for native apps, a Chrome extension bridge for in-page DOM work, and a vision fallback when neither of those surface a usable tree. Everything the agent does flows through this hub.

AI coding assistant → Terminator MCP → the desktop

Claude Code
Cursor
VS Code
Windsurf
Terminator
UI Automation
Chrome extension
OCR + vision
35 tools

Loaded 35 tools from terminator-mcp-agent. get_window_tree, click_element, type_into_element, execute_sequence, run_ai_agent, and 30 more.

stdio handshake between Claude Code and the Terminator MCP server

The six tools you will see most

Not every tool fires in every prompt. In practice, about six of the 35 cover the majority of agent turns. These are the ones to internalize if you are auditing how your Claude Code or Cursor session spends its tool budget.

get_window_tree

Returns the live accessibility tree for a process, with optional DOM, OCR, and vision overlays. The agent's primary sensor.

click_element

Invokes the UIA Invoke pattern on a selector match. No pixel math, no screenshot. Works on Win32, WPF, UWP, WinUI, and Chrome.

type_into_element

Clipboard-optimized typing with trailing {Enter} auto-detection. Fifty times faster than SendInput loops.

execute_sequence

Pack N tool calls into one atomic request. Stops on first error. This is how agents hit 95%+ success rates instead of 40%.

navigate_browser

Chrome extension bridge. The agent controls tabs with the user's cookies and session, not a headless puppet.

run_ai_agent

Fallback agentic loop. Gemini 2.5 Computer Use model takes over only when deterministic selectors fail.

The one install line

One command for Claude Code. A JSON block for the others. Same binary, same tool list, same behavior.

~/.cursor/mcp.json
terminal

The last timing is real: in a typical session, five tool calls run in roughly two seconds because Terminator keeps the accessibility tree cached between calls in the same turn. The listicle-style automation frameworks, even the fastest browser-only ones, do not have an equivalent of this because their tool boundary is the script, not the MCP turn.

Why execute_sequence is the bridge

The biggest risk in agentic UI automation is nondeterminism compounding across turns. If every tool call opens a new window tree scan and the agent re-plans from scratch, flakiness explodes. execute_sequence solves it: pack N tool calls into one atomic request, and Terminator runs them in order, with a single cached tree and stop_on_error semantics. The agent sends this once, and the next time the same flow is needed, the same JSON replays exactly.

execute_sequence request, built by Claude Code

Five steps from zero to an agent driving Notepad

Wiring Claude Code into the Windows desktop

1

Install the MCP server

One command. claude mcp add terminator "npx -y terminator-mcp-agent@latest" for Claude Code. For Cursor and VS Code, drop the equivalent JSON block into the MCP config file. The npx wrapper downloads the native Windows binary and pins the version.

2

Restart the agent

The agent reads the MCP config on start. On first launch, it handshakes with the server over stdio, asks for the tool list, and registers all 35 names into its own context. You will see them in the agent's tool UI next to whatever else you have mounted.

3

Prompt a goal, not a script

Tell the agent what you want. Open my open invoices in QuickBooks and export them to CSV. Check the build status on the Azure Pipelines tab in Chrome and if it failed, read the last 50 lines of the error output. The agent picks which of the 35 tools to call. You do not write a page object.

4

The agent resolves selectors on the live tree

get_window_tree is almost always the first call. The tree is cached for the turn, then click_element and type_into_element fire against selectors the agent generated from the tree. Selectors look like role:Button && name:Export. The agent also has spatial operators available, but most flows do not need them.

5

execute_sequence for the transactional path

Once a flow works, the agent can wrap the whole thing in a single execute_sequence call. That locks the steps in, stops on first error, and re-runs the same flow deterministically on the next invocation. This is the bridge between agentic work and reliable automation.

The numbers on this page, from the source

0
MCP tools in server.rs
0%+
success rate with execute_sequence
0x
faster than ChatGPT Agents, Claude, Perplexity Comet
0
listicle competitors that ship an MCP server for desktop

The 95% and 100x numbers come from the project's README claims, tied to the determinism of accessibility-tree automation vs frame-by-frame screenshot agents. The 35 is a hard count from source. The 0 is what I found reading the top eight ranking pages in April 2026.

The category, in a strip

Here are the UI automation tools that rank for this query, in the order the listicles list them. Each is valid software. Each is also built for a human to drive. Terminator sits at the end, in a different column of the category entirely.

SeleniumPlaywrightCypressAppiumKatalonTestCompleteRanorexTestimMablACCELQLambdaTestBrowserStackApplitoolsRobot FrameworkTestSpriteUiPathPower Automate DesktopTerminator MCP

Terminator versus the listicle picks

FeatureTypical SERP listicle UI automation toolTerminator
Primary userQA engineer in an IDEClaude Code, Cursor, VS Code agent mode
Install into the agentNot possible, no MCP surfaceclaude mcp add terminator npx -y ...
Scope of automationBrowser only (Playwright, Selenium) or browser+mobile (Appium)Every Windows desktop app + browsers + file I/O
Number of callable tools0 MCP tools, or 15-20 for Playwright MCP35, counted from #[tool(...)] in server.rs
Deterministic replay formatScreenshot-based recording, driftsAccessibility-tree event log, replays 1:1
Fallback when selector failsTest errors, engineer investigatesrun_ai_agent takes over with Gemini Computer Use
LicenseProprietary, per-seat or per-botMIT, mediar-ai/terminator on GitHub

Every MCP tool Terminator exposes, in one strip

If you hover on the strip below the scroll pauses, so you can read each name. This is the full 35-tool surface that your agent sees after a single install.

get_window_treeclick_elementtype_into_elementpress_keyopen_applicationnavigate_browserscroll_elementselect_optionset_toggledmouse_dragcapture_screenshotvalidate_elementwait_for_elementactivate_elementset_range_valueinvoke_elementhighlight_elementexecute_sequencedelayask_userzoomrun_ai_agentread_filewrite_fileedit_filecopy_contentglob_filesgrep_filestypecheck_workflowstop_all_workflowshide_inspect_overlaystop_highlightspress_key_globalget_applications_and_windows_list

What you lose by picking a GUI tool in 2026

A GUI-first UI automation tool is not wrong, it is just orthogonal to where most automation work is moving. If your team is already using Cursor or Claude Code to write tests, a browser-only recorder does not help the agent drive the legacy desktop app the tests exercise. The agent wants a tool list. Terminator is that list, MIT licensed, installed in one command. The same binary that a human invokes via the CLI is the binary the agent invokes via MCP.

One command: claude mcp add terminator "npx -y terminator-mcp-agent@latest"

Evaluating UI automation tools for an AI coding assistant?

Bring your current stack. We will show you how the 35 MCP tools map onto what you already automate, and where the agent beats the recorder.

Frequently asked questions

What counts as a UI automation tool in 2026?

Traditionally, any software that drives a graphical interface without a human moving the mouse. The commodity list has not moved in a decade: Selenium, Playwright, Cypress, Appium, TestComplete, Ranorex, Katalon, UiPath, Power Automate Desktop, Automation Anywhere, LambdaTest, BrowserStack, Applitools. Every one of them either ships an IDE for a human tester or a recorder that writes a script. The category quietly grew a second branch around 2024 when the Model Context Protocol landed: UI automation tools that are not apps at all, just a bundle of callable tools the AI coding assistant holds in its context window. Terminator is in that second branch. It exposes 35 tools over MCP, and the primary user is Claude Code or Cursor, not a QA engineer with a mouse.

How many tools does Terminator's MCP server actually expose?

35. Run grep -c '#\[tool(' crates/terminator-mcp-agent/src/server.rs against the repo and you will count exactly that many annotations. The list includes get_window_tree (scan the accessibility tree of a running process), click_element, type_into_element, press_key, open_application, navigate_browser, scroll_element, select_option, set_toggled, capture_screenshot, validate_element, wait_for_element, execute_sequence (chain multiple tool calls into one deterministic block), zoom, mouse_drag, read_file, write_file, edit_file, grep_files, glob_files, copy_content, stop_all_workflows, typecheck_workflow, and the agentic loop run_ai_agent. That last one is the Gemini 2.5 Computer Use model wired in as a fallback when deterministic selectors are not enough. No other tool on the top-ranking lists does this.

Why does MCP matter for UI automation tools specifically?

Because the primary new user of a UI automation tool is no longer a QA engineer, it is a coding agent. Claude Code, Cursor, VS Code's Agent mode, and Windsurf all speak MCP. When you install an MCP server, the agent sees the tool list in its context. The agent picks which tool to call based on the user's natural-language goal: find the OK button, type my password, check the error dialog, close the modal. The agent does not need a GUI. It needs a list of tools with clear names, clear arguments, and return values it can read back. Terminator is designed around that interface. Playwright MCP exists for browser-only control. Terminator MCP runs against the whole desktop.

What is the one-line install for Claude Code?

claude mcp add terminator "npx -y terminator-mcp-agent@latest". Restart Claude Code. Type a goal: open Chrome, navigate to github.com, find the issues tab, filter by label. Claude will plan the tool calls, resolve selectors against the live accessibility tree, and execute. No test script, no fixture, no page object. The same binary works for Cursor and VS Code through their MCP config files, and for any custom client via the stdio transport.

Which UI automation tools can Claude or Cursor actually drive today?

Playwright has an MCP server, but it is browser-only and runs headless by default. Puppeteer has community MCP wrappers, same limitation. Microsoft's Playwright Test recorder is a standalone app, not an MCP tool. UiPath has API access but no official MCP bridge. Power Automate Desktop has no MCP server. That leaves Terminator as the only production-ready MCP UI automation tool that covers browsers AND native Windows apps in the same install. The combined coverage is what makes it useful for agent workflows that span more than a single tab.

Is this for QA testing, or for production agents?

Both, and the line is blurring. For QA, the 35 MCP tools include validate_element, wait_for_element, and typecheck_workflow which read cleanly as an assertion library. For production automation, execute_sequence lets you pre-record a deterministic path and only fall back to the AI agent loop when the UI shifts. The workflow recorder in crates/terminator-workflow-recorder captures a human doing a task and produces a replayable sequence. The MCP server then runs that sequence with the AI as the recovery layer.

What about macOS and Linux?

Terminator's Rust core compiles on macOS via the AX API and on Linux via AT-SPI2. The published npm, pip, and MCP binaries are Windows-only as of April 2026. The llms.txt in the repo is explicit about it. If you need desktop automation on macOS today, the core Rust crate works but the MCP agent's tools list is Windows-first. The roadmap tracks macOS MCP parity.

How is Terminator's license different from the listicle tools?

MIT. The repo is at github.com/mediar-ai/terminator. Fork it, ship it, embed it in your own product, commercial or not. Most of the commercial UI automation tools on the SERP lists are proprietary with per-seat pricing or per-bot pricing that starts above $1000/year. The open-source ones on the list (Selenium, Appium, Playwright) are browser-first. Terminator is the only MIT-licensed UI automation tool in 2026 that covers the full Windows desktop AND exposes itself as an MCP server.

terminatorDesktop automation SDK
© 2026 terminator. All rights reserved.