windows-screenshot-mcp-server
A Go-based Windows screenshot server that captures window/desktop regions (by title/class/pid/handle) and provides both REST endpoints and MCP (JSON-RPC 2.0) methods for screenshot and window/chrome discovery/capture. It also offers real-time WebSocket streaming and Chrome DevTools-based tab capture (requires launching Chrome with remote debugging).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No authentication/authorization is documented for REST, MCP, or WebSocket. Screenshots/streams can expose sensitive UI content; transport security (TLS) is not mentioned (WebSocket uses ws:// in example). Dependency hygiene and CVE status are not assessable from provided content.
⚡ Reliability
Best When
You control the host environment (Windows machine), Chrome launching parameters, and network access to the server, and you want simple local automation/agent integration via REST, WebSocket, and MCP.
Avoid When
You need robust security boundaries for remote/public access, or you cannot guarantee safe handling of screenshots/streaming over the network and OS-level privacy constraints.
Use Cases
- • Automated UI testing and visual regression
- • Agent-driven desktop automation and monitoring
- • Capturing specific application windows by PID/title/class/handle
- • Real-time streaming of window content to clients
- • Chrome tab screenshotting via DevTools for automation/testing
Not For
- • Production deployments in untrusted multi-tenant environments without added auth/network controls
- • Use cases requiring strong compliance guarantees (not evidenced in provided docs)
- • Headless/non-Windows environments (Windows API dependency implied)
Interface
Authentication
The README describes REST endpoints, WebSocket streaming, and MCP JSON-RPC POST /rpc but does not document authentication, authorization, or access control.
Pricing
Agent Metadata
Known Gotchas
- ⚠ WebSocket streaming endpoints are described but not documented with an explicit reconnection/backoff strategy.
- ⚠ Chrome tab capture requires Chrome to be started with --remote-debugging-port and (optionally) a temp profile; agent workflows must ensure this is set up.
- ⚠ No auth is documented; agents should assume endpoints may be reachable only on trusted networks/environments.
- ⚠ Streaming sessions and max sessions are mentioned (StreamMaxSessions default 10), but session lifecycle limits/error behaviors are not documented in detail.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for windows-screenshot-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.