Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-screenshot take a screenshot of the current workspace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for taking Linux / Wayland screenshots via grim and slurp.
Exposes 2 tools to capture the full screen, a selected region, or an interactive crop — returned inline as base64 or saved to disk.
Tool | Purpose |
Capture screen (full / geometry / interactive select) | |
List available Wayland outputs / monitors |
Related MCP server: graphics-mcp
Wayland compositor (Sway, Hyprland, etc.)
grim — screenshot tool
slurp — interactive region selector
wlr-randr (optional) — for list_outputs
Install on Arch Linux:
sudo pacman -S grim slurp wlr-randrclaude mcp add screenshot -s user \
--env WAYLAND_DISPLAY=wayland-1 \
--env XDG_RUNTIME_DIR=/run/user/1000 \
-- /path/to/mcp-screenshot/.venv/bin/python /path/to/mcp-screenshot/server.pyBuild the venv once:
cd /path/to/mcp-screenshot
uv venv --python 3.12 .venv
uv pip install --python .venv/bin/python mcpKo-fi: https://ko-fi.com/kamaru
Portfolio / general: k.kamarux@gmail.com
Commercial / licensing: contact@likezara.com
Copyright © 2026 likezara™. All rights reserved. Developed by Kamaru (pen name).
List available Wayland outputs (monitors).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose behavioral traits. It only says 'list available outputs' with no mention of side effects, read-only nature, or other behaviors. This is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence that is front-loaded and efficient. No wasted words—every character earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters and the presence of an output schema, the description is minimally viable. However, it could add context on what information the output contains (e.g., names, resolutions) or that it's a safe read operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so baseline is 4. The description adds no parameter semantics, which is acceptable as schema coverage is 100% and there are no params to describe.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool lists Wayland outputs (monitors). The verb 'list' and resource 'outputs' are specific, and it distinguishes from the sibling tool 'take_screenshot' which captures an image.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool vs alternatives. While the sibling is for capturing, the description doesn't provide context or scenarios, but the purpose is clear enough to infer usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Take a screenshot of the Linux desktop.
Args: region: Optional region to capture. Use "select" to interactively pick a region with slurp, or pass geometry like "100,200 400x300". If omitted, captures the full screen. output_path: Optional path to save the screenshot. If omitted, saves to a temp file and returns the image as base64.
| Name | Required | Description | Default |
|---|---|---|---|
| region | No | ||
| output_path | No |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It explains parameter behaviors (interactive region selection, base64 return) but does not disclose potential system dependencies (e.g., X11/Wayland) or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, well-structured with clear 'Args' section, and contains no redundant information. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers core functionality and parameter options. It mentions base64 return (implying output schema), but omits image format, resolution, or platform prerequisites. Given the tool's simplicity, it is nearly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description fully specifies the 'region' parameter (including interactive 'select' and geometry format) and the 'output_path' parameter (default temp file + base64 return).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Take a screenshot'), the target ('Linux desktop'), and distinguishes from the sibling tool 'list_outputs' which serves a different purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives. The only sibling is 'list_outputs', but no comparison or usage context is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.1list_outputstake_screenshotThe two tools have clearly distinct purposes: list_outputs lists monitors, take_screenshot captures the screen. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern in snake_case (list_outputs, take_screenshot), which is predictable and clear.
With only 2 tools, the server is minimal but still reasonably scoped for basic screenshot functionality. It is slightly under the ideal 3-15 range but not problematic.
The server covers essential screenshot needs (full screen, region capture) and provides monitor listing. Missing advanced features like window capture or delay, but these are minor gaps.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server for visual regression testing: triage a PR's UI diffs from your coding agent.
MCP server to assist with JxBrowser development.
Screenshot and HTML render MCP server for AI agents
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/KamaruSama/mcp-screenshot'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
