take_screenshotLABSCO SUMMARY
Window capture that survives high-DPI displays.
Naive Windows capture clips shadows and borders and comes out fuzzy on scaled displays; this handles both, waits for the window to render after focusing it, and checks bounds when the window sits near a screen edge. Process-name matching is the practical touch — asking for "notepad" rather than an exact title is usually what you meant. Before adopting it, note the author's own pointer to the successor repository.
What it is
An MCP server that lets an AI client inside WSL capture the Windows desktop. It drives PowerShell and .NET Windows Forms behind the scenes, handles DPI scaling, and converts paths between WSL and Windows formats so either style works.
What you get
- One capture call covering four targets: all monitors by default, a named monitor, a window matched by title, or a window matched by process name —
take_screenshot - Save-location control through a
folderparameter that accepts WSL paths, Windows paths or relative paths, creating the directory if it does not exist - DPI awareness plus padding around the window, so captures on high-DPI displays are not clipped at the shadows and borders
- Helpful failure: when a window is not found, the available windows are listed rather than leaving you guessing
Requirements
Windows with WSL, Node.js installed inside WSL, and an MCP client that supports it. Clone the repository, run npm install, and point the client at index.js with node. Note that the repository is now read-only: the author has replaced it with the WSLSnapIt-MCP repository and recommends that instead. The package is screenshot-mcp-server (1.2.0 in package.json).
Setup effort
Build from source — git clone https://github.com/peterparker57/screenshot-mcp.git
USE CASES
01
Showing the assistant what is on screen
Capture all monitors or just the primary one and let the client read the resulting image.
02
Capturing one application's window
Match it by partial title or by process name, with padding and DPI handling so the frame is not clipped.
03
Filing screenshots where the work is
Pass a folder in either WSL or Windows form and let the server create it and convert the path.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/peterparker57/screenshot-mcp.git
cd screenshot-mcp
npm installMCP Clients
Claude Desktop, Claude Code
JSON
{
"mcpServers": {
"screenshot": {
"command": "node",
"args": [
"<YOUR_PATH_TO_SCREENSHOT_MCP>/index.js"
],
"disabled": false,
"alwaysAllow": [
"take_screenshot"
]
}
}
}
