Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Windows screenshots, OCR, and redacted screen recording for AI agents. No desktop app needed.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account dimitar-radenkov, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (6.7.163) reached the registry 14 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Asset Notation
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Read and maintain an Asset Notation file on disk: net worth, holdings, valuations, CSV import.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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).
| I want to... | Use | First example |
|---|---|---|
| Give my agent eyes on the desktop, and optionally hands | MCP server | Ask the agent to list your displays; it calls list_displays |
| Script captures, OCR and recordings, or gate an agent on a verified pass | CLI | pointframe displays, then pointframe verify run |
| Capture, annotate and record by hand | Desktop app | Press Print Screen |
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).
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.
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.
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.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
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.
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.
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.
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 :
Older links point to these headings. The content now lives in its own file.
Moved to the MCP reference.
Moved to PRIVACY.md.
Moved to PRIVACY.md.