Pointframe MCP Server

Pointframe

Let your coding agent test the real Windows UI.

Pointframe lets agents inspect your app, interact with its controls, and run repeatable checks with screenshots and signed evidence.

Free, open source, Windows x64.

Set up your agent | Download the screenshot app

Coding agents: read the complete Windows desktop verification recipe before starting.

An agent checks its UI change in the real app

pointframe verify run runs your build and test gates and, for each scenario in the spec, launches your built app, drives it through its real controls (invoke, type, check), and writes a verdict with a signed evidence bundle: report.json, evidence/ screenshots and an index.html. A good scenario also carries a negative control, a check with a deliberately wrong expectation that must fail.

30-second demo on the same sample: fail, fix, pass, evidence. Click to watch.

This is a real evidence screenshot from a passing run of the WPF sample (its reference spec is in the repo, so you can reproduce it).

Pick your door

The CLI and the MCP server run on their own: neither needs the tray app. Capture, OCR and recording only observe. Interacting with an app's controls is off until you set it up for one app (pointframe verify setup, or a policy file; see desktop testing).

What the MCP server gives an agent

Eleven always-on tools: list_displays, list_windows, capture_monitor, capture_window, read_text_from_monitor, read_text_from_window, search_captures, get_capture, start_recording, stop_recording and get_recording_status. Captures come back inline as an image plus a PNG on disk with SHA-256, monitor geometry and DPI. The opt-in desktop_* tools launch an approved app, click, type and check its UI, and write a signed report. Details: MCP reference.

What the CLI gives a script

pointframe displays

pointframe windows pointframe capture --monitor '\\.\DISPLAY1' --output .\shot.png pointframe ocr --monitor '\\.\DISPLAY1' pointframe record --monitor '\\.\DISPLAY1' --seconds 10 --output .\take1.mp4 pointframe verify run

The discovery, capture, OCR and recording commands write a single-line JSON response to standard output, on success and on failure. Exit code 0 is success and 1 a runtime failure with a stable Error.Code. Invalid command-line arguments exit 2 and write usage text to standard error instead of JSON. For other commands, follow their command-specific output contracts in the CLI reference and the verify docs. pointframe mcp serve speaks the MCP stdio protocol. record needs ffmpeg.exe. Every command and flag: CLI reference.

Quick start

Set up your agent

• Claude Code plugin. From a clone, claude --plugin-dir ./plugin/pointframe starts the MCP server and adds the verify-desktop-work skill (plugin README). The plugin is not yet in the plugin directory.
• Other MCP clients (Claude Desktop, Codex, Cursor, VS Code): connect your MCP client.
• CLI. Download Pointframe.Cli-win-x64.zip from the latest release, extract it, and run this from that folder (checksum step: CLI install). Open a new terminal afterwards, so the user Path change takes effect. Then pointframe displays lists your monitors, and the verify guide covers your own app.

.\Pointframe.Cli.exe install

Download the screenshot app

winget install DimitarRadenkov.Pointframe

Press Print Screen to capture a region, add arrows, text or blur, then copy, save, pin or record. Or take the installer from Releases. Features, settings and shortcuts: desktop app guide.

FAQ

Does it need the desktop app? No. The CLI and the MCP server are standalone: no tray app and no .NET runtime. The desktop app is the separate screenshot tool for people.

Can it run headless? Build and test gates can, including in CI. Checks of the real UI need an unlocked, interactive Windows session; a Windows service in session 0 cannot capture the user desktop.

What does a pass establish? That the gates and scenarios your spec configures all passed. A spec with only gates passes without launching an app, so UI coverage is only what your scenarios check. Trust a pass only when pointframe verify status reports fresh: true. Freshness covers the Git-visible working tree, the spec and the active-task snapshot. A spec with scenarios but no gates can pass but is never fresh (no_build_gate). Files ignored by .gitignore and verify's own output are not counted. It does not prove your code is correct.

Privacy and telemetry

Official release builds of the CLI and the MCP server send anonymous usage counts (command or tool name, outcome, duration bucket, host, MCP client type, version, a random install ID), never screenshots, text or paths. Opt out with POINTFRAME_TELEMETRY_OPTOUT=1 or DO_NOT_TRACK=1; this applies to the CLI and the MCP server only. The desktop app's official builds send the events listed in PRIVACY.md, which holds the full policy; source builds send nothing.

Links

CLI reference | MCP reference | Desktop app guide | Verify docs | Developer guide | Privacy | Contributing | Releases | Website

If you find Pointframe useful, a star on GitHub helps others discover it.

If Pointframe saves you time, consider buying me a beer :

Moved sections

Older links point to these headings. The content now lives in its own file.

Pointframe MCP Server

Moved to the MCP reference.

Privacy Policy

Moved to PRIVACY.md.

Privacy & Telemetry

Moved to PRIVACY.md.