What is the recommended workflow for WSL2?
The recommended workflow uses `save_screenshot_to_host_workspace` with WSL workspace path; the server converts it to a UNC path, saves the screenshot, and returns `"success"`.
@KunihiroS
基本情報
MCP Server for local screen shot.
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"Screenshot-server": {
"command": "powershell.exe",
"args": [
"-Command",
"Invoke-Command -ScriptBlock { cd '<YOUR_WINDOWS_PROJECT_PATH>'; & '<YOUR_WINDOWS_UV_PATH>' run screenshot.py }"
]
}
}
}** Takes a screenshot, converts the provided WSL path to a UNC path, and saves the file to the Host's workspace. Automatically detects the WSL distribution name.
`host_workspace_path` (str): The absolute WSL path of the Host's workspace (e.g., `/home/user/project`).
** `str` - `"success"` or `"failed: [error message]"`.
`name` (str, optional): Filename. Defaults to `latest_screenshot.jpg`.
** `str` - Absolute path or `"failed: [error message]"`.
`path` (str, optional): Target directory (Windows or UNC path). Defaults to server's working directory.
** `str` - `"success"` or `"failed: [error message]"`.
Screenshot Server is an MCP (Modular Communication Protocol) server that captures screenshots and saves them to a file path specified by the client, enabling AI assistants or other processes to access the screenshot via its file path.
Deploy the server on Windows (required for capturing the Windows screen), install dependencies with uv sync, and configure the MCP host to launch it (e.g., via PowerShell in WSL). Use the provided tools: save_screenshot_to_host_workspace, take_screenshot_and_return_path, or take_screenshot_path.
server.log.images/ directory and returns the absolute path.The recommended workflow uses `save_screenshot_to_host_workspace` with WSL workspace path; the server converts it to a UNC path, saves the screenshot, and returns `"success"`.
Three tools: `save_screenshot_to_host_workspace` (recommended), `take_screenshot_and_return_path`, and `take_screenshot_path`.
It saves to a path specified by the client: either the host’s workspace (via UNC path conversion), a local `images/` directory, or an arbitrary directory given as a Windows or UNC path.
Python 3.x, dependencies `mcp[cli]>=1.4.1`, `pyautogui`, and `Pillow`, installed via `uv sync`. The server must run directly on Windows to capture the screen.
DOM-first AI browser automation for Chrome and MCP clients.

Parse allows your agent to access thousands of APIs instantly. You can use Parse to build an API for any action on any website and edit any previously existing API in our catalogue.
This MCP server provides browser automation capabilities through Puppeteer, allowing interaction with both new browser instances and existing Chrome windows.

Model Context Protocol Servers
BitBrowser MCP simple to use, no complicated procedures required. Supports a variety of intelligent agent services.
コメント