webdev-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listScreensA | List available screens/displays that can be captured |
| takeScreenshotA | Take a screenshot of a specific screen and return it as a base64 encoded string. |
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 2 tools
listScreens and takeScreenshot have clearly distinct purposes—one lists available screens, the other captures a screenshot. There is no overlap or ambiguity between them.
Both tools use a consistent camelCase verb_noun pattern (listScreens, takeScreenshot) that is predictable and clear.
With only 2 tools, the set is minimal but covers the essential operations for screen capture (list and capture). Could be slightly thin but still reasonable for a focused domain.
The tool set covers listing screens and capturing a screenshot, which is the core functionality. Missing features like capturing all screens or with options are minor gaps that agents can work around.