web-browser-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REQUEST_TIMEOUT | No | The request timeout period in seconds for the web-browser-mcp-server. |
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 |
|---|---|
| browse_webpageC | Extract content from a webpage with optional CSS selectors for specific elements |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined as extracting webpage content with optional element selection.
The single tool name follows a clear verb_noun pattern (browse_webpage). Since there are no other tools to compare against, consistency is inherently perfect.
A single tool for a web browser server is too minimal for the apparent scope. Basic web interactions like navigation, clicking, form filling, or handling multiple tabs are missing, making the server feel incomplete and limiting for agents.
The server is severely incomplete for a web browser domain. It only offers content extraction, lacking essential operations such as navigation, interaction with page elements, or session management, which are critical for typical web automation tasks.