browser-inspector-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_inspectA | Inspects a live browser page to get CSS and DOM information — the same data a human sees in browser DevTools. Use this before writing or debugging CSS to verify what the browser actually renders, not just what the source code says. Four actions available: 'dom' gets the rendered HTML structure, 'styles' gets the full CSS cascade, 'screenshot' captures a visual snapshot, 'diff' compares styles before and after a change. Call with action 'help' if unsure. |
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 confusion or overlap between tools, making disambiguation perfect. The tool's description clearly outlines its distinct purpose of inspecting browser pages, with no competing tools to cause misselection.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'browser_inspect' follows a clear verb_noun pattern, and with no other tools to compare, there are no deviations or inconsistencies in naming conventions.
A single tool is too few for a server named 'browser-inspector-mcp', which suggests a broader scope for browser inspection tasks. While the tool covers multiple actions (dom, styles, screenshot, diff), the server feels thin and under-scoped, as typical inspection domains might benefit from more specialized or separate tools.
The tool provides core inspection actions (dom, styles, screenshot, diff), but there are notable gaps for a browser inspector, such as missing tools for network monitoring, JavaScript debugging, performance analysis, or element interaction. This limits the server's ability to fully cover browser inspection workflows, though the included actions are useful for basic CSS and DOM tasks.