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 |
|---|---|
| run_browser_agentD | Handle run-browser-agent tool calls. |
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 'run_browser_agent' has a distinct purpose that cannot be confused with any other tool in this set.
The naming pattern cannot be inconsistent with only one tool. The tool name 'run_browser_agent' follows a clear verb_noun pattern, and there are no other tools to create naming conflicts or mixed conventions.
A single tool is generally too few for most server purposes, as it limits functionality and may not cover the domain adequately. For a browser automation server, one tool feels thin and restrictive compared to typical expectations of multiple actions like navigation, clicking, or form filling.
The tool surface is severely incomplete for browser automation. With only one tool to run an agent, there are obvious gaps in core operations such as navigating to URLs, interacting with page elements, extracting data, or managing browser sessions, which will likely cause agent failures in practical use.