Screenshot MCP Server
About
Capture Windows screenshots from AI assistants in WSL, with options for specific monitors or windows.
Details
- Author
- peterparker57
- Categories
- Productivity
Jump to
Setup
Install Screenshot MCP Server in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/peterparker57/screenshot-mcp
Follow the installation instructions in the repository README, then restart your MCP client.
Capture Windows screenshots from AI assistants in WSL, with options for specific monitors or windows.
This repo is in Read Only mode and has been replaced
Use the WSLSnapIt-MCP repo instead (works better, more features!)
A Model Context Protocol (MCP) server that enables AI assistants running in WSL to capture Windows screenshots with advanced features like monitor selection and window-specific capture.
- πΈFull Desktop Capture- Capture all monitors (default behavior)
- π₯οΈMonitor Selection- Capture specific monitors (primary, 1, 2, etc.)
- πͺWindow Capture- Capture specific windows by title match with DPI awareness
- πProcess Capture- Capture windows by process name (e.g., notepad.exe)
- πCustom Save Locations- Save to any folder using WSL or Windows paths
- πAutomatic Path Conversion- Converts WSL paths to Windows paths
- πOrganized Storage- Screenshots saved toworkspace/screenshots/by default
- π―DPI Aware- Proper scaling for high-DPI displays
- πΌοΈFull Window Capture- Includes window shadows and borders without clipping
- Windows with WSL (Windows Subsystem for Linux)
- Node.js installed in WSL
- Claude Desktop or Claude Code with MCP support
git clone https://github.com/peterparker57/screenshot-mcp.git cd screenshot-mcp
- Add to your Claude configuration (~/.claude.jsonor~/.claude/claude_desktop_config.json):
{ "mcpServers": { "screenshot": { "command": "node", "args": [ "/path/to/screenshot-mcp/index.js" ], "disabled": false, "alwaysAllow": [ "take_screenshot" ] } } }
Once installed, you can ask Claude to take screenshots:
Take a screenshot of monitor 1 Take a screenshot of the primary monitor
Take a screenshot of the "Chrome" window Take a screenshot of window titled "Visual Studio Code"
Take a screenshot of notepad.exe Take a screenshot of the chrome process Take a screenshot of process "Code"
Take a screenshot and save it as "test.png"
Take a screenshot and save it to /mnt/c/Users/username/Pictures/ Take a screenshot and save to C:\Users\username\Desktop\ Take a screenshot of monitor 1 and save to folder "../docs/images"
- filename(optional): Name for the screenshot file (default: "screenshot.png")
- monitor(optional): Which monitor to capture
- "all"- Capture all monitors (default)
- "primary"- Capture primary monitor only
- 1,2, etc. - Capture specific monitor by index
- Supports WSL paths:/mnt/c/Users/...
- Supports Windows paths:C:\Users\...
- Supports relative paths:../images
- Default:workspace/screenshots/
- Success message with the file path
- Error message if capture fails
- If bothwindowTitleandprocessNameare provided,windowTitletakes precedence
- Custom folders are created automatically if they don't exist
- Path formats are automatically converted between WSL and Windows as needed
- MCP Server: Node.js with@modelcontextprotocol/sdk
- Screenshot Capture: PowerShell with .NET Windows Forms
- Communication: Executes PowerShell commands from WSL
- Encoding: Base64 encoding for reliable command execution
- DPI Awareness: Automatically handles high-DPI displays for crisp captures
- Window Padding: Adds 10px padding to capture window shadows and borders
- Render Wait: Waits 200ms after focusing window to ensure complete rendering
- Bounds Checking: Prevents negative coordinates when windows are near screen edges
- Process Matching: Intelligent process name matching (strips .exe extension automatically)
- MCP server receives screenshot request from Claude
- Determines save location (custom folder or default)
- Converts paths between WSL and Windows formats as needed
- Constructs appropriate PowerShell script based on parameters
- Encodes script in base64 to avoid escaping issues
- Executes PowerShell command from WSL
- PowerShell captures screenshot using Windows Forms APIs
- Image is saved to the specified location
- Filters PowerShell CLIXML output (verbose logging, not errors)
- Validates monitor indices
- Provides clear error messages for missing windows or processes
- Lists available windows when capture fails
- Automatically creates directories if needed
- Handles both WSL and Windows path formats
The server automatically creates folders as needed. Ensure you have write permissions to the target location.
- Ensure the window is open and not minimized
- The title match is case-insensitive and supports partial matches
- Try using a more specific window title
- When searching by process, the tool will list all available windows to help you identify the correct one
The latest version includes automatic padding and DPI awareness. If you still experience clipping:
- Ensure you're using the latest version
- Try maximizing the window before capture
- Check if the window has unusual rendering (some apps use custom chrome)
The server automatically converts between WSL and Windows path formats:
- WSL paths like/mnt/c/...are converted toC:\...for PowerShell
- Windows paths likeC:\...are converted to/mnt/c/...for file verification
- Ensure your paths are accessible from both WSL and Windows
- Added custom folder support with thefolderparameter
- Supports both WSL paths (/mnt/...) and Windows paths (C:\...)
- Automatic path conversion between WSL and Windows formats
- Creates custom directories automatically if they don't exist
- Maintains backward compatibility with default screenshots folder
- Added process name capture support
- Can now capture windows by process name (e.g., "notepad.exe")
- Intelligent .exe extension handling
- Enhanced error messages showing available windows
- Fixed window capture clipping issues
- Added DPI awareness for high-DPI displays
- Added padding to capture window shadows
- Improved window rendering wait time
- Added bounds checking for edge cases
Contributions are welcome! Please feel free to submit a Pull Request.
MIT License - see LICENSE file for details
- Built for use withClaude Desktopand Claude Code
- Uses theModel Context Protocol
- Special thanks to the WSL team for making Windows/Linux integration possible
The 1Password MCP server creates a bridge that allows MCP clients such as Codex and Kiro to manage your 1Password Environments with secure authorization prompts.
This is the 1st, easiest, and cheapest PPT, slides, presentation AI generation MCP Server in the world.
Persistent memory for any AI assistant. Zero token cost until recall. Stores memories in local SQLite, ranks by 6-factor scoring, returns results 79% smaller than JSON. Works with Claude, ChatGPT, Grok, Cursor, Windsurf, and any MCP client.
A MCP server that enables AI assistants to interact with Anki, the spaced repetition flashcard application.
Enables LLM clients to interact with macOS applications through AppleScript. Built using the @beyondbetter/bb-mcp-server library, this server provides safe, controlled execution of predefined scripts with optional support for arbitrary script execution.
An MCP server for WordPress plugin audits
Turn your AI assistant into a digital marketing hub that creates, organizes, and analyzes links and QR Codes on demand.
Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.
Sync Calendars, Scheduling Links, AI Executive Scheduling Assistant, Unified Calendar
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.



