screen-capture-mcp
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_monitorsA | List connected monitors with their numbers, resolutions, positions, and which is primary. |
| capture_screenA | Take one screenshot of a monitor and return it as an image. Args: monitor: "primary", "all" (every screen stitched together), or a monitor number (1 = leftmost). See list_monitors. max_dimension: Longest edge of the returned image in pixels (256-4096). The default balances legibility and token cost; raise it only when small text is unreadable. image_format: "jpeg" (smaller, default) or "png" (lossless, crisper small text). |
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 2 tools
The two tools have completely distinct purposes: list_monitors enumerates displays, while capture_screen takes a screenshot. There is no overlap or chance of misselection.
Both names follow the same verb_noun snake_case convention (list_monitors, capture_screen), making the set highly predictable.
Two tools is on the lean side, but for a tightly scoped screen-capture server they cover the essential list-then-capture workflow. A minor addition could enrich it, but nothing feels extraneous.
The core lifecycle of discovering monitors and capturing them is covered, with thoughtful options for monitor selection, sizing, and format. Gaps remain around region/window capture or recording, but the stated purpose is well served.