Browsershot 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 |
|---|---|
| screenshotA | Take a browser screenshot of a URL. Returns the image file path. Use this to visually verify frontend changes, check responsive layouts, or debug CSS issues. The returned file path can be viewed with the Read tool. |
| screenshot_compareA | Take screenshots at multiple viewport widths to compare responsive layouts. Returns file paths for mobile (375px), tablet (768px), and desktop (1440px) by default. |
| page_infoA | Get page metadata: title, viewport size, scroll height, fonts, colors, and resource counts. Useful for auditing a page without a full screenshot. |
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 3 tools
Each tool has a clearly distinct purpose: page_info extracts metadata without rendering, screenshot captures a single viewport, and screenshot_compare generates multiple viewports for responsive testing. No functional overlap or ambiguity exists.
Mixed structural patterns: page_info follows noun_noun (describing output data), while screenshot and screenshot_compare use noun or noun_verb patterns (describing actions). All use snake_case, but semantic consistency is lacking compared to a uniform verb_noun convention.
Three tools is lean but appropriate for a focused screenshot utility. The set covers auditing (page_info), basic capture (screenshot), and responsive validation (screenshot_compare) without unnecessary proliferation.
Core screenshot workflow is well-covered including metadata inspection and multi-device responsive testing. Minor gaps might include PDF generation or granular viewport control (e.g., single mobile screenshot without the full comparison set), but the essential surface supports complete screenshot tasks.