Browser-Use MCP Server
Related Servers
Alternatives to Browser-Use MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables browser automation through a headless browser page, letting agents navigate to URLs, click, hover, fill and select form elements, capture screenshots, and evaluate JavaScript in the page.275 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables browser automation through MCP with native Playwright operations, deterministic assertions, and natural-language grounded actions, structured extraction, and bounded agent workflows over live page elements.13Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive a Chromium-based browser for web research, testing, and automation with Playwright-compatible tools, persistent profiles, proxy matching, extension loading, and humanized input across local or containerized deployments.431 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform Playwright-compatible browser automation with persistent profiles, Chrome extension support, proxy matching, humanized input, and npm/Docker deployment over stdio or Streamable HTTP.431 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform Playwright-compatible browser automation with persistent profiles, proxy routing, extension loading, and humanized mouse, keyboard, and scroll interactions over stdio, Streamable HTTP, npm, or Docker.431 npmMIT
- AlicenseAqualityDmaintenanceEnables browser automation with anti-detection features, including navigation, interaction, form filling, and session management.2236 PyPI10MIT
This server cannot be deployed
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 clearly distinct purpose with no other tools to confuse it with.
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 deviate from this convention.
A single tool is too few for a server named 'Browser-Use MCP Server', which suggests a broader scope for browser automation. One tool feels thin and inadequate for handling various browser-related tasks like navigation, clicking, or form filling.
The tool set is severely incomplete for browser automation. With only a 'run_browser_agent' tool, there are obvious gaps in basic operations such as opening pages, interacting with elements, or retrieving content, making it impossible for agents to perform typical browser tasks.