Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Motion sensor for AI agents: tells when a screen region changes or goes still. Scores, never pixels.
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.
PIR_CAPTURE_CMD, PIR_SELECT_CMD, PIR_WINDOW_GEOMETRY_CMD, PIR_PICK_WINDOW_CMD, PIR_MAX_WAIT_MSYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pir": {
"command": "npx",
"args": [
"-y",
"pir-mcp"
],
"env": {
"PIR_CAPTURE_CMD": "your-value",
"PIR_SELECT_CMD": "your-value",
"PIR_WINDOW_GEOMETRY_CMD": "your-value",
"PIR_PICK_WINDOW_CMD": "your-value",
"PIR_MAX_WAIT_MS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add pir --env PIR_CAPTURE_CMD=your-value --env PIR_SELECT_CMD=your-value --env PIR_WINDOW_GEOMETRY_CMD=your-value --env PIR_PICK_WINDOW_CMD=your-value --env PIR_MAX_WAIT_MS=your-value -- npx -y pir-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pir": {
"command": "npx",
"args": [
"-y",
"pir-mcp"
],
"env": {
"PIR_CAPTURE_CMD": "your-value",
"PIR_SELECT_CMD": "your-value",
"PIR_WINDOW_GEOMETRY_CMD": "your-value",
"PIR_PICK_WINDOW_CMD": "your-value",
"PIR_MAX_WAIT_MS": "your-value"
}
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"pir": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"pir-mcp"
],
"env": {
"PIR_CAPTURE_CMD": "your-value",
"PIR_SELECT_CMD": "your-value",
"PIR_WINDOW_GEOMETRY_CMD": "your-value",
"PIR_PICK_WINDOW_CMD": "your-value",
"PIR_MAX_WAIT_MS": "your-value"
}
}
}
}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.
PIR_CAPTURE_CMD envPIR_SELECT_CMD envPIR_WINDOW_GEOMETRY_CMD envPIR_PICK_WINDOW_CMD envPIR_MAX_WAIT_MS envThese 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 Solteris-Dev, 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 (0.1.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, sync. labs
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.
Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.
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.
A motion sensor for AI agents.
*"Gives your LLM agents enough info to be a helpful "watcher" without being a privacy nightmare like Windows Recall"* *-Solteris-Dev*
A PIR sensor tells you *that* something moved, never *what*. This is the same idea for a screen: an MCP server that watches named rectangles and answers "did this change?" and "has this gone still?" with a number, a size and a timestamp. No tool in it returns pixels, image files, or anything that could be turned back into a picture.
It exists because an agent driving a desktop keeps needing the same two things: *wake me when the build output moves* and *tell me if this status bar has stopped ticking*. Both are motion questions. Neither needs a screenshot.
still_for_ms, or time out. A short window means "the animation settled, safe to act". A long window on something that should keep changing means it is frozen, and still=true is the alarm.Every comparison reports two numbers over a coarse grid of averaged colour cells (at most 64 across, each at least 4 px), both 0 for identical and 1 for black against white:
metric=peak for a small thing that should tick inside a larger region.Averaging is what makes this a sensor rather than a camera: 64 cells cannot be read.
pir_pick_region carries a purpose line the agent has to write down before you draw.What it *does* reveal, so you can decide whether that is acceptable: that a given rectangle changed, at a given time, by a given magnitude. On a region covering a chat window that is presence information. Choose regions accordingly; the server has no opinion.
The capture itself is delegated to a command you configure, run with your privileges. The default is grim, so nothing here has screen access that you did not already give to grim.
It is on npm as pir-mcp and in the official MCP Registry as io.github.Solteris-Dev/pir-mcp, so most clients can run it with npx -y pir-mcp and no clone:
claude mcp add -s user pir -- npx -y pir-mcp
From source:
git clone https://github.com/Solteris-Dev/pir-mcp
cd pir-mcp && npm install && npm run build
Requires Node 20+ and a screenshot tool that can write binary PPM to stdout.
PIR_CAPTURE_CMD is a template; {x} {y} {w} {h} are substituted and the result runs under sh -c. It must print a binary PPM (P6) to stdout.
| environment | command | |
|---|---|---|
| wlroots / Hyprland / Sway (default) | grim -g "{x},{y} {w}x{h}" -t ppm - | |
| X11 with maim | `maim -g {w}x{h}+{x}+{y} -f png \ | magick png:- ppm:-` |
| X11 with ImageMagick | import -window root -crop {w}x{h}+{x}+{y} +repage ppm:- | |
| macOS | `screencapture -x -R{x},{y},{w},{h} -t png /dev/stdout \ | magick png:- ppm:-` |
Coordinates are whatever the capture tool uses. On a wlroots layout that is the global layout, so an output placed left of the primary has negative x.
PIR_SELECT_CMD runs when an agent calls pir_pick_region or pir_pick_mask and must print x,y wxh. Set it to an empty string to remove those tools entirely.
| environment | command |
|---|---|
| wlroots / Hyprland / Sway (default) | slurp -f "%x,%y %wx%h" |
| X11 | slop -f "%x,%y %wx%h" |
| macOS | see contrib/macos (untested) |
PIR_WINDOW_GEOMETRY_CMD gets {id} substituted and must print x,y wxh for that window; PIR_PICK_WINDOW_CMD must print the id of the window the person chose. Both default to Hyprland (via jq and slurp -r). Set either to an empty string to remove the corresponding tools. Window ids are limited to [A-Za-z0-9_.:-] before they reach a shell.
| environment | geometry | pick | |||||||
|---|---|---|---|---|---|---|---|---|---|
| Hyprland (default) | `hyprctl -j clients \ | jq -r --arg id "{id}" '.[] \ | select(.address==$id) \ | "\(.at[0]),\(.at[1]) \(.size[0])x\(.size[1])"'` | visible windows as slurp boxes, prints the address | ||||
| Sway | `swaymsg -t get_tree \ | jq -r '.. \ | select(.id? == {id}) \ | "\(.rect.x),\(.rect.y) \(.rect.width)x\(.rect.height)"'` | `swaymsg -t get_tree \ | jq -r '.. \ | select(.visible? == true) \ | "\(.rect.x),\(.rect.y) \(.rect.width)x\(.rect.height) \(.id)"' \ | slurp -r -f '%l'` |
| X11 | `xdotool getwindowgeometry --shell {id} \ | awk -F= '/^X/{x=$2}/^Y/{y=$2}/^WIDTH/{w=$2}/^HEIGHT/{h=$2}END{print x","y" "w"x"h}'` | xdotool selectwindow |
Only the Hyprland pair has been run; the others are written from the tools' documentation.
claude mcp add -s user pir -- npx -y pir-mcp
claude mcp add -s user pir -- node /path/to/pir-mcp/dist/stdio.js
Blocking calls default to 55 s and are capped by PIR_MAX_WAIT_MS (540 s). Keep the cap under your host's MCP tool timeout; an agent that needs to watch for longer just calls again.
| variable | default | meaning |
|---|---|---|
PIR_REGIONS | unset | JSON file of regions to define at startup |
PIR_THRESHOLD | 0.05 | default change threshold |
PIR_INTERVAL_MS | 500 | default sampling period |
PIR_DEFAULT_WAIT_MS | 55000 | default timeout for blocking calls |
PIR_MAX_WAIT_MS | 540000 | cap for blocking calls |
PIR_CAPTURE_TIMEOUT_MS | 10000 | how long one capture may take |
PIR_SELECT_TIMEOUT_MS | 60000 | how long the person has to draw a selection |
PIR_MAX_CELLS | 64 | grid resolution on the long side; smaller is coarser and more private |
A regions file looks like:
[
{ "name": "bar", "x": 0, "y": 0, "w": 1920, "h": 26, "masks": [{ "x": 1690, "y": 0, "w": 110, "h": 26 }] } ]
The case that produced this: a status bar that occasionally froze for hours while its process looked healthy. The clock in it should change every minute, so a bar that is still for three minutes is a frozen bar.
pir_pick_region name=bar purpose="watch the status bar for a freeze"
pir_wait_for_stillness name=bar still_for_ms=180000 metric=peak timeout_ms=540000
still=true comes back only if the bar stopped; otherwise the call returns still=false at the timeout and the agent calls again. Nothing on the screen was ever seen, and the person drew the rectangle themselves.
contrib/macos/ holds an AppKit rectangle selector and capture recipe, written blind and untested. If you run it on a real Mac, fix what breaks and send it back.
npm test
MIT.