Screenshot FAQs

Question 1

How does Screenshot integrate with WSL?

Accepted Answer

Screenshot is designed to run on Windows. When used with a WSL host it captures the screen, converts WSL paths to Windows-accessible UNC paths, and saves the screenshot to the specified location within the host's WSL filesystem.

Question 2

What is Screenshot and what does it do?

Accepted Answer

Screenshot is an MCP server that captures screenshots and saves them to file paths specified by the client. It's designed for seamless integration with other processes and AI assistants, particularly those running in WSL.

Question 3

How do I specify the filename of the screenshot?

Accepted Answer

All available tools accept an optional `name` argument, which allows you to specify the desired filename. The default filename varies depending on the tool used.

Question 4

What are the different tools available in Screenshot?

Accepted Answer

Screenshot provides three tools: `save_screenshot_to_host_workspace` (recommended for WSL integration), `take_screenshot_and_return_path` (returns the absolute path of the saved screenshot), and `take_screenshot_path` (saves to an arbitrary location specified by a Windows or UNC path).

Question 5

Where should I run the Screenshot server?

Accepted Answer

The Screenshot server must run directly on Windows to capture the Windows screen, even when used with a WSL-based AI assistant. See the setup and usage documentation for the recommended configuration.

Screenshot

Screenshot

Key Features

Use Cases

Key Features

Use Cases