MCP ScreenCatch
Click on "Install 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 ScreenCatchcapture a screenshot of the error message on my second monitor"
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 ScreenCatch
An MCP (Model Context Protocol) server that provides screen capture functionality for Claude Desktop, emulating Windows Snipping Tool capabilities.
Overview
MCP ScreenCatch enables Claude Desktop to capture screenshots of user-selected screen regions. The tool allows users to highlight areas of their monitor(s), capture them, and save the images with timestamps for easy retrieval and processing.
Related MCP server: Screen View MCP
Objectives
Seamless Integration: Provide an MCP command that Claude Desktop can invoke to initiate screen captures
Interactive Selection: Allow users to select specific regions of their screen(s) using a familiar snipping interface
Multi-Monitor Support: Work across multiple monitors for flexible screen capture
Sequential Captures: Enable users to capture multiple screenshots in succession without restarting the tool
Timestamped Files: Automatically timestamp each capture for chronological ordering
Configurable Output: Let users specify the output directory for captured images
Pipeline Ready: Save files in a location accessible to other MCP commands or external applications
Features
Core Functionality
Region Selection: Click and drag interface to select screen regions
Capture & Save: Button/icon to finalize and save the selected region
Continuous Mode: After each capture, prompt user to:
Capture another screenshot
Quit the tool
Timestamp Naming: Files named with ISO 8601 timestamps (e.g.,
capture_2025-11-27_064730.png)Directory Selection: User-configurable output directory
Use Cases
Capture UI elements for debugging
Document visual workflows
Create sequential tutorials or guides
Feed captured images to Claude for analysis
Build visual documentation pipelines
Technical Implementation
MCP Protocol
The tool will be exposed as an MCP server that Claude Desktop can connect to, providing:
Tool:
capture_screen- Initiates the screen capture interfaceTool:
set_output_directory- Configure where captures are savedTool:
list_captures- Retrieve timestamped capture files
Technology Stack
Language: TypeScript/Node.js
MCP SDK: @modelcontextprotocol/sdk
Screen Capture: screenshot-desktop for cross-platform screen capture
Image Processing: Sharp for image cropping and manipulation
UI Framework: Electron for transparent overlay and region selection
File Format
Default format: PNG (lossless, good for UI captures)
Naming convention:
capture_YYYY-MM-DD_HHMMSS.pngMetadata: Optional JSON sidecar with capture timestamp and dimensions
Installation
npm install
npm run buildConfiguration
Add to Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"screencatch": {
"command": "node",
"args": ["/path/to/mcp-screencatch/build/index.js"]
}
}
}Usage
From Claude Desktop
Once configured, you can ask Claude to capture screenshots:
Claude, can you capture a screenshot of my screen?Interactive Overlay
An Electron overlay window will appear covering your screen(s)
Click and drag to select the region you want to capture
Click the Capture button or press Enter to save
Press ESC or click Cancel to abort
The captured image is saved with a timestamp
Available Commands
Capture a screenshot:
Claude, capture a screenshotSet output directory:
Claude, set the screenshot output directory to C:\Users\johne\screenshotsList recent captures:
Claude, list my recent screenshotsFile Naming
Screenshots are automatically named with ISO 8601 timestamps:
capture_2025-11-27_143052.pngcapture_2025-11-27_143105.png
This ensures chronological ordering and prevents filename conflicts.
Development Status
✅ Implemented - Core functionality complete
✅ MCP server with stdio transport
✅ Interactive region selection with Electron overlay
✅ Timestamped file naming
✅ Configurable output directory
✅ List and manage captures
⚠️ Note: Requires Electron, which adds ~150MB to node_modules. For production use, consider electron-builder for packaging.
Future Enhancements
Support for full screen and window captures
Multiple image format options (PNG, JPG, WebP)
Annotation tools (arrows, text, highlights)
Clipboard integration
Automatic cleanup of old captures
Screenshot comparison tools
License
MIT
Contributing
Contributions welcome! Please open an issue or submit a pull request.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceA Model Context Protocol server that enables natural language-driven screenshot capture on macOS, allowing users to take full desktop screenshots, capture specific windows, or select custom screen areas through Claude Desktop.Last updated
- AlicenseDqualityDmaintenanceEnables AI assistants to capture and analyze screenshots using Claude Vision API, providing AI-powered insights about desktop interface content, UI elements, and visual layouts.Last updated2222MIT
- Alicense-qualityDmaintenanceEnables Claude Desktop to interactively capture and analyze Zoho CRM timeline screenshots, automatically extracting timeline events, workflows, and functions through OCR and vision API, with export to JSON and Markdown formats.Last updatedMIT
- Alicense-qualityAmaintenanceEnables Claude to capture and analyze screen content across Windows, macOS, and Linux with zero native runtime dependencies.Last updated205MIT
Related MCP Connectors
Generate images, GIFs, and PDFs from HTML, URLs, or templates — from your AI agent.
Screenshots, PDFs and Markdown from any URL or HTML for AI agents, via the SnapForge API
Screenshot, diff, audit and sitemap-capture any web page — 5 MCP tools for AI agents.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/johnelamont/mcp-screencatch'
If you have feedback or need assistance with the MCP directory API, please join our Discord server