Summary
Show it rather than describe it.
Describing what is on screen is where most debugging conversations lose their footing. A region capture with the image embedded in the reply puts the actual pixels in front of the model, and the saved path means the file is still there afterwards.
What it is
Screen capture on Windows over MCP: whole monitors, all monitors at once, or an interactively selected region, saved to a screenshots folder and optionally embedded in the reply.
What you get
- A full-screen capture across all monitors, or one monitor by number
- An interactive area selection for a targeted crop
- The saved path, the captured rectangle and its dimensions returned with every shot
- Optional base64 embedding, so the image arrives in the response and not only on disk
- A listing of the captures already taken
- A capture timeout you can set
Requirements
Windows, a recent Node.js, and the RegionSnip.exe helper present at bin/RegionSnip.exe — capture runs through it, so put it in place before the first call. Runs from npx with no account or key.
Setup effort
One command — npx mcp-windows-screenshot