Skip to content
Back to search

unified-test-mcp

An MCP server that lets an AI agent test a running Vaadin Flow app in a real browser, in terms of Vaadin components rather than DOM nodes

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 17 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/mvysny/unified-test-mcp with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/mvysny/unified-test-mcp'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mvysny--unified-test-mcp/badge.svg)](/listings/mvysny--unified-test-mcp)

HTML

<a href="/listings/mvysny--unified-test-mcp"><img src="/api/listings/mvysny--unified-test-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 61 lines
  1. # Unified Test MCP
  2. An MCP (Model Context Protocol) server that lets an AI agent test a running Vaadin Flow app in
  3. a real browser, in terms of Vaadin components rather than DOM nodes: `Button "Save"`, a text
  4. field by its label, a Grid's rows. The component knowledge comes from the Unified API for
  5. Vaadin UI tests running on Playwright; this project owns the MCP tools on top of it.
  6. ## Status
  7. A prototype with four tools:
  8. - `snapshot()` — the Vaadin components on the page, one line each, each with a `ref` the other
  9. tools take:
  10. ```
  11. URL: http://localhost:8080/form
  12. Title: Form
  13. - TextField "Name" [ref=1, id=name, value="Alice"]
  14. - Button "Save" [ref=4] actions: click
  15. ```
  16. - `navigate(url)` — opens that URL, a full page load; says so when the app has no view there.
  17. Returns the new snapshot.
  18. - `click(ref)` — clicks the component; returns the snapshot once the server has handled the
  19. click.
  20. - `get_text(ref)` — a Button's or a Span's text.
  21. - `get_value(ref)` — a field's value as JSON, uncut; a ComboBox's item by the label the user
  22. sees; whether a Checkbox is ticked.
  23. - `get_helper(ref)`, `get_tooltip(ref)` — the helper text below a field, a component's tooltip;
  24. uncut, where the snapshot cuts them at 120 characters.
  25. Set ids on the components your tests touch: the snapshot shows them, so what an agent finds
  26. carries straight into a Java test.
  27. What's next is in [design/ideas/](design/ideas/).
  28. ## Running
  29. The server is one jar, `unified-test-mcp-<version>.jar`, from the GitHub releases page; it
  30. needs Java 21 or newer. Register it with Claude Code:
  31. ```bash
  32. claude mcp add vaadin-test -- java -jar /path/to/unified-test-mcp-<version>.jar
  33. ```
  34. Options, after the jar: `--browser-executable <path>` to use an installed Chromium instead of
  35. Playwright's own download, `--headed` to watch the browser. The browser starts on an empty page
  36. and goes where the agent navigates, so tell the agent the app's URL; the app needs to be up only
  37. by then.
  38. ## Building
  39. A JDK 21 or newer. `./gradlew` builds everything and runs the tests; the server's jar lands in
  40. `unified-test-mcp/build/libs/unified-test-mcp-<version>.jar`.
  41. `test-app` is a Vaadin app to test against: `./gradlew :test-app:run`, then
  42. http://localhost:8080. The start view has the button `clicker`; the view at `second` has the
  43. button `back`, which returns to the start view; the view at `form` has a few fields and buttons.
  44. Try it: start `test-app`, register the jar you built as above, start `claude`, and ask it to
  45. open http://localhost:8080, click the button `clicker` twice and tell you its text, or to go to
  46. `form` and save.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.