viewpo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIEWPO_PORT | No | Port the Viewpo bridge server listens on | 9847 |
| VIEWPO_AUTH_TOKEN | Yes | Bearer token from Viewpo Settings → MCP Bridge |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| viewpo_screenshotA | Capture screenshots of a URL at one or more viewport widths. Returns base64 JPEG images. Use this to SEE what a webpage looks like at different screen sizes. |
| viewpo_get_layout_mapA | Extract the DOM layout tree of a URL at a given viewport width. Returns element hierarchy with tags, classes, bounding rects, and computed CSS styles. Use this to understand page structure and find layout issues. |
| viewpo_compare_viewportsA | Compare the layout of a URL at two different viewport widths. Returns a list of elements whose size or CSS styles differ between the two viewports. Use this to find responsive design issues. |
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: compare_viewports for detecting differences, get_layout_map for structural analysis, and screenshot for visual capture. There is no overlap in functionality, making it easy for an agent to select the right tool based on the task.
All tool names follow a consistent 'viewpo_' prefix with descriptive snake_case suffixes (compare_viewports, get_layout_map, screenshot). This predictable pattern enhances readability and reduces confusion.
With 3 tools, the server is well-scoped for its viewport testing domain, but it feels slightly thin. While each tool is useful, additional tools like viewpo_get_metrics or viewpo_simulate_device might enhance completeness without being overwhelming.
The tools cover core viewport analysis tasks: layout comparison, structure extraction, and visual capture. However, there are minor gaps, such as missing tools for performance metrics or device simulation, which agents might need to work around for advanced testing scenarios.