Browser-use 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 |
|---|---|
| execute_browser_taskC | 执行浏览器自动化任务 |
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 between tools. The single tool 'execute_browser_task' has a clearly distinct purpose that cannot be confused with any other tool in the set.
The naming is perfectly consistent as there is only one tool, following a clear verb_noun pattern ('execute_browser_task'). No other naming conventions are present to cause inconsistency.
A single tool for a browser automation server is too few for the apparent scope, as browser automation typically involves multiple operations like navigation, clicking, typing, or scraping. This feels thin and may limit functionality.
The tool surface is severely incomplete for browser automation, lacking essential operations such as navigating to URLs, interacting with elements, or extracting data. This will likely cause agent failures in handling common browser tasks.