Easily access and manage Windows Screenshots from WSL2. List and retrieve screenshots with metadata, paths, or base64 co
by rubinsh·Read, analyze, and understand files in your project
Example: Summarize README, analyze code structure, find TODO comments across codebase
Navigate large codebases 5x faster, understand projects quickly
Create, move, rename, and organize files based on natural language instructions
Example: Organize downloads by file type, rename files following convention, batch process images
Save hours on manual file organization
Search files for patterns, extract data, find information across directories
Example: Find all config files with API keys, extract emails from documents, search logs for errors
Find information instantly instead of manual grep/find
Generate boilerplate files, apply templates, create project structures
Example: Create React component with tests and styles, generate OpenAPI spec, scaffold new project
Eliminate repetitive file creation work
MetaTag Genie
MetaTag Genie uses AI to write standardized metadata to image formats like HEIC and PNG, helping you automate tagging an
Eyevinn Open Source Cloud
Eyevinn Open Source Cloud lets AI assistants deploy and manage multi-vendor cloud infrastructure with an open source API
Nutrient Document Web Services
Integrate Nutrient Document Web Services API for secure PDF manipulation, digital signing, and document processing acros
Desktop Commander
Desktop Commander MCP unifies code management with advanced source control, git, and svn support—streamlining developmen
Advanced MCP Server
Advanced MCP Server: real-time NWS weather alerts, NewsAPI news search, and a safe local business directory for AI assis
Windows Screenshots reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend Windows Screenshots for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
I recommend Windows Screenshots for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Windows Screenshots reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Windows Screenshots reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated Windows Screenshots against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Windows Screenshots is the kind of server we cite when onboarding engineers to host + tool permissions.
According to our notes, Windows Screenshots benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Windows Screenshots is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We wired Windows Screenshots into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
showing 1-10 of 30
Share your MCP server with the developer community
Select a client to integrate this server.
Claude Desktop configuration
{
"mcpServers": {
"windows-screenshots": {
"command": "npx",
"args": [
"mcp-windows-screenshots@latest"
],
"env": {
"WINDOWS_USERNAME": "YourWindowsUsername",
"MCP_SCREENSHOT_DIRS": "/mnt/c/Users/YourWindowsUsername/Pictures/Screenshots"
}
}
}
}Enables Claude to access Windows screenshots directly from WSL2 environments by automatically detecting screenshot directories and providing tools to list and retrieve screenshot files.
Windows Screenshots is a community-built MCP server published by rubinsh that provides AI assistants with tools and capabilities via the Model Context Protocol. Easily access and manage Windows Screenshots from WSL2. List and retrieve screenshots with metadata, paths, or base64 co It is categorized under file systems.
You can install Windows Screenshots in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
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.
<a href="https://glama.ai/mcp/servers/@rubinsh/mcp-windows-screenshots"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@rubinsh/mcp-windows-screenshots/badge" alt="Windows Screenshots MCP server" /> </a> <p align="center"> <img src="./demo.gif" alt="MCP Windows Screenshots Demo" width="800"> </p>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:
No more copy-pasting paths or navigating directories!
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@latest
That's it! Restart Claude Code and you're ready to go.
The tool will automatically:
Once installed, Claude can use these tools:
Ask Claude: "Look at the latest screenshot"
Claude will automatically find it and look at the image.
Ask Claude: "Show me my latest screenshots"
Claude will display your recent screenshots with timestamps and sizes.
Ask Claude: "Which directories are you checking for screenshots?"
Claude will show all configured paths.
The tool automatically:
claude mcp list to verify the server is installed-s user when adding the serverIf your screenshots are saved in a non-standard location, you can specify custom directories:
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@latest
claude mcp add windows-screenshots -s user -e "MCP_SCREENSHOT_DIRS=C:\Users\john\CustomFolder;C:\Users\john\Desktop" -- npx mcp-windows-screenshots@latest
WINDOWS_USERNAME: Override the auto-detected Windows usernameMCP_SCREENSHOT_DIRS: Specify custom screenshot directories (semicolon-separated for multiple paths)If the auto-detection doesn't find the correct username:
claude mcp add windows-screenshots -s user \
-e "WINDOWS_USERNAME=YourWindowsUsername" \
-- npx mcp-windows-screenshots@latest
claude mcp add windows-screenshots -s user -e "WINDOWS_USERNAME=YourWindowsUsername" -- npx mcp-windows-screenshots@latest
To contribute or modify this tool:
git clone https://github.com/rubinsh/mcp-windows-screenshots.git
cd mcp-windows-screenshots
npm install
npm run build
MIT © rubinsh
Time estimate: 10-20 minutes including configuration
Prerequisites
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server provides file I/O operations (read, write, search, metadata) as tools Claude can invoke with natural language instructions.
Protocols
Compatibility
✓ Use when
Use for code analysis, file organization, content search, template generation, and automating repetitive file operations. Best for local development workflows.
✗ Avoid when
Avoid for system-critical files, sensitive credentials, production environments, or when file integrity is paramount. Don't use on files you can't afford to lose.