self-healing-browser-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_navigateC | Open a URL in the shared browser page and return the final URL. |
| browser_snapshotA | Return the page's interactive elements as roles + accessible names. Use this to 'see' the page semantically before deciding what to click or type. |
| browser_clickA | Click an element described by any combination of locator strategies. Provide as many as you know (e.g. |
| browser_fillC | Type |
| browser_get_textC | Return the visible text of the described element. |
| browser_assert_visibleC | Assert the described element is present and visible. Returns PASS or FAIL. |
| browser_closeA | Close the browser and release its resources. |
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 7 tools
Each tool targets a distinct action (navigate, snapshot, click, fill, get text, assert visibility, close) with no overlap. The descriptions clearly differentiate their purposes.
All tools follow a consistent 'browser_verb_noun' pattern in snake_case, making the set predictable and easy to understand.
The server has 7 tools, which is well-scoped for a browser automation server. Each tool provides a necessary function without redundancy or bloat.
The tool set covers core browser operations (navigation, interaction, state inspection, assertion). Minor gaps like scrolling or waiting exist but do not critically hinder typical agent workflows.