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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listScreensB | 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
The two tools have clearly distinct purposes: listScreens enumerates available displays, while takeScreenshot captures a specific screen. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool based on the task.
The naming is mixed: listScreens uses camelCase, while takeScreenshot uses camelCase but with a different verb style (list vs. take). Both are readable, but they lack a consistent pattern like verb_noun or uniform casing, which could cause minor confusion in a larger set.
With only 2 tools, the server feels thin for a web development domain, which typically involves more operations like browser control, DOM manipulation, or network monitoring. This limited scope may restrict agent capabilities and suggests an incomplete tool surface.
For a webdev-mcp server, the tools only cover screen listing and screenshot capture, leaving significant gaps in web development workflows such as page navigation, element interaction, or performance testing. The surface is severely incomplete for the implied domain, likely causing agent failures in broader tasks.