browser-use MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UV_PUBLISH_TOKEN | No | Your token used for publishing. | |
| UV_PUBLISH_PASSWORD | No | Your password for publishing. | |
| UV_PUBLISH_USERNAME | No | Your username for publishing. |
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 |
|---|---|
| add-noteC | Add a new note |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-notes | Creates a summary of all notes |
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 confusion between tools. The tool 'add-note' has a clear and distinct purpose that cannot be misselected against other tools.
Since there is only one tool, it inherently follows a consistent naming pattern. The tool name 'add-note' uses a verb_noun format, which is clear and predictable, and there are no other tools to cause inconsistency.
A single tool is too few for a server named 'browser-use', which suggests a broader scope related to browser interactions. This minimal set feels thin and incomplete for the implied domain, limiting functionality.
The tool set is severely incomplete for a browser-use server. With only an 'add-note' tool, there are obvious gaps in core browser operations like navigation, clicking, or form filling, making it inadequate for typical browser automation tasks.