home / mcp / domshot mcp server
Fetches browser screenshots of DOM elements via an MCP server for automated visual checks.
Configuration
View docs{
"mcpServers": {
"adtac-domshot": {
"command": "bash",
"args": [
"$PWD/domshot/mcp.sh"
]
}
}
}Domshot provides an MCP server that can fetch browser screenshots of DOM elements. It enables automated capture and description of visuals from a web page, which is useful for visual testing, UI reviews, and accessibility checks.
To use the server with an MCP client, first ensure the MCP server is running in your environment. Then, on the page you want Claude to capture a screenshot from, embed the client script in your page and ask Claude to invoke the screenshot tool. You can describe the result after Claude returns the image and its description.
Steps you can follow in practice: - Add the embedding script to the target page - Request a browser screenshot via the MCP tool - Review the description of the resulting image and iterate as needed.
Example usage flow (conceptual): paste the embed script into the page, then command Claude to call get_browser_screenshot and describe what you see in the screenshot.
Install prerequisites and set up the MCP integration with these steps.
$ git clone https://github.com/adtac/domshot.git
$ claude mcp add domshot -- $PWD/domshot/mcp.sh
Restart Claude.The MCP server is configured via the standard MCP flow where you register the server with your MCP client and provide the command to run the server script. The server script for this project is located under domshot/mcp.sh and is referenced during the MCP registration process.
Usage notes: - The browser screenshot tool fetches the visual state of a DOM element or page area and returns a description suitable for accessibility checks and UI reviews. - Ensure the page you target is reachable by the environment that runs the MCP server and that any required permissions for script embedding are granted.
- Only embed the script on pages you control or that you have permission to instrument. - If you encounter connection or embedding issues, verify that the MCP server is running and that the embedding script was loaded on the target page. - Restart the MCP client or server if new configurations are applied.
Captures a browser screenshot of the target DOM area and provides a visual description suitable for automated review.