WSLSnapit-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| take_screenshotA | WSLSnapIt: Smart screenshot capture for WSL. Capture monitors, windows by title/process, with direct image return and auto-compression. |
| read_clipboardB | Read the current Windows clipboard content (text or image) |
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: one reads clipboard content (text or image), while the other captures screenshots. There is no overlap in functionality, making it impossible to confuse them.
Both tools follow a consistent verb_noun naming pattern: 'read_clipboard' and 'take_screenshot'. The naming is clear, predictable, and uses the same convention throughout.
With only two tools, the server feels thin for a general-purpose utility server. While the tools are specific to clipboard and screenshot operations, the scope is limited, and more complementary tools (e.g., for image processing or file management) might be expected.
For a clipboard and screenshot utility, basic read/capture operations are covered, but there are notable gaps. For example, there is no tool to write to the clipboard, edit screenshots, or manage captured images, which could limit agent workflows.