Windows Screenshots logo

Windows Screenshots

Community
rubinsh

MCP tool for easier screenshots when working on windows with WSL2

Publisherrubinsh
Repositorymcp-windows-screenshots
LanguageJavaScript
Forks
3
Stars
6
Available tools
0
Transport typestdio
Categories
LicenseMIT
Links
  • Connect tools to AI workflows

    Windows Screenshots exposes MCP capabilities that can be used by compatible AI clients and agents.

  • 0 available tools

    Browse the callable actions below, including names and descriptions when provided by the server.

  • Ready-to-copy setup

    Use the installation snippets to configure this server in your preferred MCP client.

  • Open source signals

    6 stars and 3 forks from the linked repository.

MCP Windows Screenshots

npm version License: MIT

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:

  1. Take a screenshot on Windows (Win+Shift+S)
  2. Ask Claude to show your latest screenshot/s
  3. 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

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):

bash
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:

  • 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:

  1. Detects your environment (WSL2 vs native Windows)
  2. Queries Windows registry for your actual Screenshots folder location
  3. 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

  1. Ask Claude to "list screenshot directories" to see which paths are being searched
  2. Ensure your screenshots are saved in one of the searched directories
  3. If your screenshots are in a custom location, see Advanced Configuration below

Tool not available

  1. Restart Claude Code after installation
  2. Run claude mcp list to verify the server is installed
  3. Ensure you used -s user when 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:

bash
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

Windows with custom paths:

bash
claude mcp add windows-screenshots -s user -e "MCP_SCREENSHOT_DIRS=C:\Users\john\CustomFolder;C:\Users\john\Desktop" -- npx mcp-windows-screenshots@latest

Environment Variables

  • WINDOWS_USERNAME: Override the auto-detected Windows username
  • MCP_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:

bash
claude mcp add windows-screenshots -s user \
  -e "WINDOWS_USERNAME=YourWindowsUsername" \
  -- npx mcp-windows-screenshots@latest

Windows:

bash
claude mcp add windows-screenshots -s user -e "WINDOWS_USERNAME=YourWindowsUsername" -- npx mcp-windows-screenshots@latest

Development

To contribute or modify this tool:

bash
git clone https://github.com/rubinsh/mcp-windows-screenshots.git
cd mcp-windows-screenshots
npm install
npm run build

License

MIT © rubinsh

Installation

TypingMind
Prerequisites:

Node.js 18+

{
  "mcpServers": {
    "windows-screenshots": {
      "command": "npx",
      "args": [
        "mcp-windows-screenshots@latest"
      ],
      "env": {
        "WINDOWS_USERNAME": "YourWindowsUsername",
        "MCP_SCREENSHOT_DIRS": "/mnt/c/Users/YourWindowsUsername/Pictures/Screenshots"
      }
    }
  }
}

Use Windows Screenshots MCP with multiple AI models

TypingMind connects MCP tools at the workspace level, so once Windows Screenshots is connected, you can use it with different AI models in TypingMind instead of setting it up separately for each model. This MCP runs locally through the TypingMind MCP connector on your device.

Setup guide to use the local connector

Use this when the MCP server needs access to local files, apps, or private resources on your computer.

1

Open the MCP settings

In TypingMind, go to Settings, Advanced Settings, then Model Context Protocol and choose Setup Connector.

  1. Open TypingMind in your browser.
  2. Click the Settings icon.
  3. Go to Advanced Settings.
  4. Open the Model Context Protocol section.
  5. Click Setup Connector and choose This Device.
TypingMind MCP connector setup screen with This Device selected
2

Run the connector command

Choose This Device, copy the command from TypingMind, and run it in Terminal. Keep the process running while you use MCP.

  1. Copy the setup command shown by TypingMind.
  2. Open Terminal on macOS or Windows Terminal on Windows.
  3. Paste and run the command.
  4. Approve the package install if Terminal asks you to proceed.
  5. Keep the Terminal window running while using MCP tools.
3

Add Windows Screenshots as a server

When the connector status is Ready, click Edit Servers and paste the MCP server configuration.

  1. Wait until the connector status shows Ready.
  2. Click Edit Servers.
  3. Paste the Windows Screenshots MCP server configuration.
  4. Save the server list.
  5. Refresh if you want to confirm the connector is still ready.
TypingMind MCP settings showing active server and Edit Servers button
{
  "mcpServers": {
    "windows-screenshots": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-windows-screenshots"
      ]
    }
  }
}
4

Use it across models

Save the server list, open Plugins, enable the Windows Screenshots MCP tools, then select any supported AI model in TypingMind and use the tools in chat or assign them to an AI agent.

  1. Open the Plugins page in TypingMind.
  2. Enable the Windows Screenshots MCP tools.
  3. Start a chat and choose the AI model you want to use.
  4. Use the MCP tools in chat or assign them to an AI agent.
  5. Switch to another AI model whenever needed without reconnecting MCP.
TypingMind chat using enabled MCP tools with a selected AI model
Can you use Windows Screenshots to help me with this task?
Windows Screenshots
Sure. I read it.
Here is what I found using Windows Screenshots.

Frequently asked questions

What is the Windows Screenshots MCP server used for?

Windows Screenshots is an MCP server that lets compatible AI clients connect to external tools and context. In TypingMind, you can add this MCP server once and make its tools available in your AI workspace.

Can I use Windows Screenshots MCP with multiple AI models in TypingMind?

Yes. TypingMind connects MCP tools at the workspace level, so you can use Windows Screenshots with different AI models such as Claude, ChatGPT, Gemini, or other models you have configured in TypingMind without setting up the MCP server separately for each model.

Why use Windows Screenshots MCP with TypingMind?

TypingMind is one of the best frontends for LLM chat because it brings multiple AI models, prompts, plugins, AI agents, API keys, and MCP tools into one workspace. With Windows Screenshots connected, you can use its MCP tools across your preferred models while keeping your chat workflow organized in TypingMind.

How do I connect Windows Screenshots MCP to TypingMind?

Windows Screenshots runs through the TypingMind local MCP connector. This is best when the MCP server needs access to local files, desktop apps, command-line tools, or private resources on your computer.

What tools does Windows Screenshots MCP provide in TypingMind?

Windows Screenshots exposes MCP capabilities that can be enabled from the TypingMind Plugins page and used in chat or assigned to AI agents.

Do I need to share my API keys with TypingMind to use Windows Screenshots MCP?

No. TypingMind is local-first and lets you keep your model providers, API keys, prompts, and MCP configuration under your control. If Windows Screenshots requires authentication, add the required headers, OAuth settings, or local configuration for that MCP server when you create the connection.

Related MCP Servers

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇