Browser MCP Server
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 |
|---|---|
| browser-consoleB | Navigate to a URL and capture console output from the browser with streaming support |
| browser-server-consoleB | Spawn an Express static server for a directory and capture console output from the served content |
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 overlapping purposes—both capture console output from a browser—but their descriptions clarify distinct contexts: one navigates to a URL, while the other serves local content. Some ambiguity remains as both involve browser console operations, but the descriptions help differentiate them.
Both tool names follow a consistent 'browser-[context]-console' pattern, using hyphens to separate words. This predictable naming scheme makes it easy to understand their roles and relationship within the server.
With only two tools, the server feels under-scoped for a 'Browser MCP Server' that implies broader browser automation capabilities. A typical browser server might include tools for navigation, DOM interaction, or screenshots, making this set appear incomplete.
Inferred domain is browser automation, but the toolset is severely incomplete. It lacks basic operations like page navigation, element interaction, or screenshot capture, focusing narrowly on console output. This will likely cause agent failures for common browser tasks.