browser-use MCP server
Related Servers
Alternatives to browser-use MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with web pages through browser automation, supporting web scraping, form filling, navigation, and other browser-based tasks using Playwright.1MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform web automation tasks by connecting to remote Playwright/browserless instances, supporting navigation, screenshots, HTML extraction, and element interaction.104-
- FlicenseCqualityCmaintenanceProvides browser automation tools for AI assistants via the Model Context Protocol, enabling tasks like navigation, clicking, filling forms, screenshots, and script execution through natural language.39-
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.18Apache 2.0
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, generate test code, scrape web content, and execute JavaScript in a real browser environment.3211,800 npmMIT
- FlicenseNot gradedqualityCmaintenanceA Model Control Protocol server that enables AI assistants to control a browser, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.-
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.