captureAndAnalyzeScreenLABSCO SUMMARY
One call, whole screen, your own key.
The scope is deliberately narrow — no window targeting, no app list, just the full screen and a question — which makes it the shortest path from "look at this" to an answer. The design consequence worth knowing is that analysis runs against your own Anthropic key rather than the client's session, so every capture is a billable vision call you control and pay for. Pinning the version in the config is not fussiness; the README calls it out because npx caching has bitten people here.
What it is
A screenshot-and-analyse tool for MCP clients. It captures the whole screen and passes the image to the Claude Vision API along with a prompt you supply, so the assistant reasons about what is actually rendered rather than about your description of it.
What you get
- Capture and analysis as a single call, taking a
promptfor the question and amodelNameto choose which model looks at it —captureAndAnalyzeScreen - A trivial echo tool for checking the connection is alive before you debug anything else —
helloWorld - Both stdio and SSE transports, since clients differ — Claude Desktop uses stdio, while Cursor, Cline and Windsurf support either
- A Smithery deployment path with a Dockerfile and config in the repository, for hosting it over WebSocket instead of running it locally
Requirements
An Anthropic API key, supplied as ANTHROPIC_API_KEY in your client config or as a command-line argument — the vision call is billed to you, not to the client. Node.js 18+. Install globally with npm as screen-view-mcp, or launch it with npx; the README recommends pinning the exact version (2.0.15 in package.json) in your config to avoid npx cache surprises. For SSE, the built entry takes a port and host alongside the key.
Setup effort
One command plus a key — npm install -g screen-view-mcp, then supply credentials
USE CASES
01
Asking what is wrong with something on screen
Capture and ask in the same call, so the model reads the actual layout instead of your account of it.
02
Debugging a visual issue mid-session
Take a shot when the glitch appears and have it described, rather than reproducing it later from memory.
03
Documenting an interface
Point the prompt at the elements you care about and get a written description of the layout you can paste into notes.
04
Checking the server is actually connected
Call the echo tool first, so a failure is clearly connection rather than capture or API key.
2 tools
Listed in project docs. Your client may show a different list.
helloWorldBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- npx on PATH
- ANTHROPIC_API_KEY in your environment
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"screen-view-mcp": {
"command": "npx",
"args": [
"screen-view-mcp@2.0.15"
],
"transport": "stdio",
"env": {
"ANTHROPIC_API_KEY": "<YOUR_ANTHROPIC_API_KEY>"
}
}
}
}npm
TERMINAL
npm install -g screen-view-mcp
