MCP Windows Screenshots
The MCP Windows Screenshots server enables Claude to seamlessly access and manage Windows screenshots from within WSL2, eliminating manual file navigation.
• List Screenshots: View recent screenshots with options to limit results, filter by file type (PNG, JPG, GIF), or search specific directories • Get Specific Screenshot: Retrieve a screenshot by full path, returning either the file path or base64 encoded content • List Configured Directories: Display all directories currently being searched for screenshots • View Latest Screenshot: Automatically find and display the most recently taken screenshot • Flexible Configuration: Automatically searches common screenshot locations or allows custom directory setup via environment variables
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Windows Screenshots show me my latest screenshot"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Windows Screenshots
An MCP (Model Context Protocol) server that enables Claude to access Windows screenshots from WSL2. Perfect for seamlessly sharing screenshots with Claude Code without manual file navigation.
Why This Tool?
When using Claude Code cli in WSL2 or in Cursor/VSCode, sharing Windows screenshots requires navigating complex file paths like /mnt/c/Users/... or dragging the image to the terminal.
Also, what if want to share the last 4 screenshots with Claude? this can become very cubersome.
This tool simplifies the process to just:
Take a screenshot on Windows (Win+Shift+S)
Ask Claude to show your latest screenshot/s
Claude instantly accesses and displays it
No more copy-pasting paths or navigating directories!
Key Features
Auto-detection: Automatically detects your Windows Screenshots folder location from the registry
Cross-platform: Works in both WSL2 and native Windows environments
Smart defaults: Falls back to common screenshot locations if custom paths aren't found
Zero configuration: Works out of the box for most users
Related MCP server: screen-capture-mcp
Prerequisites
Windows 10/11 (with or without WSL2)
Node.js 18+
Claude Code CLI installed
Installation
Run this single command in your terminal (works in WSL2, Windows Terminal, PowerShell, or Command Prompt):
claude mcp add windows-screenshots -s user -- npx mcp-windows-screenshots@latestThat's it! Restart Claude Code and you're ready to go.
The tool will automatically:
Detect your environment (WSL2 or Windows)
Find your Windows Screenshots folder from the registry
Configure the appropriate paths
Usage
Once installed, Claude can use these tools:
View a Screenshot
Ask Claude: "Look at the latest screenshot"
Claude will automatically find it and look at the image.
List Recent Screenshots
Ask Claude: "Show me my latest screenshots"
Claude will display your recent screenshots with timestamps and sizes.
Check Screenshot Directories
Ask Claude: "Which directories are you checking for screenshots?"
Claude will show all configured paths.
How It Works
The tool automatically:
Detects your environment (WSL2 vs native Windows)
Queries Windows registry for your actual Screenshots folder location
Searches common locations as fallback:
Your configured Screenshots folder (from Windows settings)
Pictures/Screenshots
OneDrive Pictures/Screenshots
Desktop
Documents/Screenshots
Temp folders
Troubleshooting
No screenshots found
Ask Claude to "list screenshot directories" to see which paths are being searched
Ensure your screenshots are saved in one of the searched directories
If your screenshots are in a custom location, see Advanced Configuration below
Tool not available
Restart Claude Code after installation
Run
claude mcp listto verify the server is installedEnsure you used
-s userwhen adding the server
Advanced Configuration
Custom Screenshot Directories
If your screenshots are saved in a non-standard location, you can specify custom directories:
WSL2 with custom paths:
claude mcp add windows-screenshots -s user \
-e "MCP_SCREENSHOT_DIRS=/mnt/c/Users/john/CustomFolder;/mnt/c/Users/john/Desktop" \
-- npx mcp-windows-screenshots@latestWindows with custom paths:
claude mcp add windows-screenshots -s user -e "MCP_SCREENSHOT_DIRS=C:\Users\john\CustomFolder;C:\Users\john\Desktop" -- npx mcp-windows-screenshots@latestEnvironment Variables
WINDOWS_USERNAME: Override the auto-detected Windows usernameMCP_SCREENSHOT_DIRS: Specify custom screenshot directories (semicolon-separated for multiple paths)
Manual Username Configuration
If the auto-detection doesn't find the correct username:
WSL2:
claude mcp add windows-screenshots -s user \
-e "WINDOWS_USERNAME=YourWindowsUsername" \
-- npx mcp-windows-screenshots@latestWindows:
claude mcp add windows-screenshots -s user -e "WINDOWS_USERNAME=YourWindowsUsername" -- npx mcp-windows-screenshots@latestDevelopment
To contribute or modify this tool:
git clone https://github.com/rubinsh/mcp-windows-screenshots.git
cd mcp-windows-screenshots
npm install
npm run buildLicense
MIT © rubinsh
Available Tools
3 toolsget_screenshotB
Get a specific screenshot file path or content
Inputs: path (required), return_content.
list_directoriesB
List all configured screenshot directories
Inputs: no named parameters.
list_screenshotsC
List recent screenshots from Windows directories
Inputs: directory, limit, pattern.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_screenshot retrieves specific screenshot content, list_directories shows configured directories, and list_screenshots lists recent screenshots. There is no overlap in functionality, making tool selection unambiguous.
All tools follow a consistent verb_noun pattern (get_screenshot, list_directories, list_screenshots) with clear, descriptive names. The naming convention is uniform and predictable throughout the set.
With only 3 tools, the server feels somewhat thin for managing Windows screenshots. While the tools cover basic retrieval and listing, additional operations like taking new screenshots or deleting old ones might be expected, making the count borderline for the domain.
The tools provide read-only access to existing screenshots and directories, but there are notable gaps for a full screenshot management system. Missing operations include capturing new screenshots, deleting or organizing screenshots, and configuring settings, which limits agent workflows.
Maintenance
Related MCP Connectors
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Hosted Screenshots MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for capturing screen regions directly into Claude Code conversations via hotkeys or tool calls. It provides Windows-specific screen snipping with multi-monitor support, persistent storage, and automatic management of captured images.MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables Claude Code and other MCP clients to take screenshots of the full screen or specific windows, with support for repeated captures over intervals.159 npm8MIT
- AlicenseAqualityCmaintenanceMCP server that gives Claude Code reliable access to clipboard images and screenshots, fixing broken paste in iTerm2.23MIT
- AlicenseAqualityDmaintenanceMCP server enabling Claude Code to capture screenshots of Windows applications through WSL2, allowing AI to diagnose UI errors and verify layouts.11MIT