Screen Vision MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capture_fullscreenC | Capture the entire screen |
| capture_windowB | Capture a specific window by app name |
| capture_regionC | Capture a specific region of the screen |
| extract_text_from_screenC | Capture screen and extract text using OCR |
| find_text_on_screenA | Find text on screen and return its location |
| get_window_listA | Get list of all open windows with their positions |
| get_screen_infoA | Get information about available screens/displays |
| click_at_positionB | Click at a specific screen position |
| monitor_screen_regionC | Monitor a screen region for changes |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a clearly distinct action: capturing a specific target, extracting/finding text, retrieving system info, clicking, or monitoring. Even the capture variants are disambiguated by their target (fullscreen, window, region).
All tool names follow a consistent snake_case verb_noun pattern, such as capture_window, get_screen_info, and find_text_on_screen. This makes the tool set predictable and easy to navigate.
Nine tools is well-scoped for a screen vision and automation server. Each tool covers a meaningful capability without unnecessary overlap or bloat.
The tool surface covers capture, OCR, text location, screen/window information, clicking, and region monitoring. Minor gaps exist around input actions like typing or scrolling, but core workflows are well supported.