desktop_screenshot_mcp_server

This MCP server provides a set of tools to interact with your desktop screenshots via Model Context Protocol. It simulates the Windows Print Screen behavior and can capture screenshots from all monitors, just the primary display, or provide detailed information about connected displays. The available tools include TakeScreenshot (captures all monitors), TakePrimaryScreenshot (captures only the primary monitor), GetScreenInfo (lists monitor details), and SimulatePrintScreen (emulates pressing the Print Screen key). You can trigger these tools through an MCP client or via VS Code Copilot integration, enabling AI-assisted workflows to request and retrieve screenshots as image files with timestamps saved to the Desktop.

Prerequisites:

• Windows 10/11 (x64)
• .NET 10.0 SDK or Runtime
• Git (optional for manual install)
• Internet access for UVX or git operations

Option A — One-Click Install via UVX (Recommended):

1. Ensure UV and UVX are installed. If UV is not installed, you may install it first: pip install uv
2. Install the MCP server with UVX by running: uvx screenshot-mcp-server

Option B — Manual UVX Installation (alternative workflow):

1. Install UV (if not already installed): pip install uv
2. Run the server directly with UVX (if a package is available in the registry): uvx screenshot-mcp-server

Option C — Manual Installation via Git (source build):

1. Clone the repository: git clone https://github.com/metamintbtc/desktop_screenshot_mcp_server.git
2. Navigate to the project folder: cd desktop_screenshot_mcp_server
3. Build the project (requires .NET 10 SDK): dotnet build
4. Run the server locally: dotnet run --project ScreenshotMcpServer.csproj

Notes:

• The project is a .NET 10 based MCP server. Ensure the environment has .NET 10 runtime installed.
• If using UVX, the one-click URL described in the README can be used in a browser to install/import the server setup.

Tips and common notes:

• The server saves screenshots to the Desktop with a timestamped filename (e.g., screenshot_2025-08-04_18-59-30.png).
• The GetScreenInfo tool returns details such as the number of monitors, resolutions, and positions.
• Ensure the process has the necessary permissions to access screen capture APIs on Windows.
• If you customize the VS Code mcp.json, ensure the project path (--project) points to the correct ScreenshotMcpServer.csproj location on your machine.
• This MCP server is designed for Windows environments; adjust paths accordingly if running in different shells or sandboxes.