MCP Windows Screenshots
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WINDOWS_USERNAME | No | Override the auto-detected Windows username | |
| MCP_SCREENSHOT_DIRS | No | Specify custom screenshot directories (semicolon-separated for multiple paths) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_screenshotsC | List recent screenshots from Windows directories |
| get_screenshotB | Get a specific screenshot file path or content |
| list_directoriesB | List all configured screenshot directories |
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 3 tools
Each tool has a clearly distinct purpose: get_screenshot retrieves specific screenshot content, list_directories shows configured directories, and list_screenshots lists recent screenshots. There is no overlap in functionality, making tool selection unambiguous.
All tools follow a consistent verb_noun pattern (get_screenshot, list_directories, list_screenshots) with clear, descriptive names. The naming convention is uniform and predictable throughout the set.
With only 3 tools, the server feels somewhat thin for managing Windows screenshots. While the tools cover basic retrieval and listing, additional operations like taking new screenshots or deleting old ones might be expected, making the count borderline for the domain.
The tools provide read-only access to existing screenshots and directories, but there are notable gaps for a full screenshot management system. Missing operations include capturing new screenshots, deleting or organizing screenshots, and configuring settings, which limits agent workflows.