browser-use-mcp
Related Servers
Alternatives to browser-use-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables coding agents to drive a real, indexed Chrome browser over MCP stdio, navigating pages, observing numbered interactive elements, and performing click, type, and select actions without the server itself calling any model.5MIT
- AlicenseAqualityAmaintenanceEnables AI agents to drive a Chromium browser over MCP, reading pages as a numbered list of controls and performing actions like clicking, filling forms, and asserting page state without screenshots or API keys.1076 PyPI20MIT
- AlicenseNot gradedqualityAmaintenanceEnables an MCP client's LLM to drive a live browser by stating one outcome at a time, while TypeSafe System One picks the elements, actions and values and judges whether each step is done, blocked or irreversible; it also exposes tools for snapshots, targeted page reading, screenshots and calling a page's own WebMCP tools.0MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to browse the web by reading pages as short, numbered text lines and acting on controls by number. It works as an MCP server with Claude Code, Codex, Cursor or custom agents, returning only what changed after each action.01MIT
- AlicenseAqualityBmaintenanceEnables AI agents to drive a Chromium browser through MCP, with persistent sessions, compact page snapshots, guarded actions, batched operations, and explicit result verification.16MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for vision-first browser automation that annotates interactive elements with numbered markers, allowing AI agents to control any webpage by simply referencing element numbers.12MIT
TDQS
Scored across 9 tools
Tools mostly target distinct browser operations: open, re-observe, act, evaluate, screenshot, console, goal, close, and doctor are separable. The main overlap is browser_act's intent mode versus browser_goal, both policy-driven model actions, though goal is scoped to its own tab and an overall objective.
All tools use a consistent browser_ prefix, making them easy to recognize as one family. Suffixes mix nouns (browser_page, browser_screenshot, browser_console) and verbs (browser_open, browser_close, browser_act), which is a minor deviation but still readable and predictable.
Nine tools is well-scoped for a browser automation server. Each tool covers a meaningful part of the browser-control lifecycle without obvious redundancy or filler.
The surface covers opening, observing, acting, evaluating JavaScript, screenshotting, console inspection, autonomous goals, closing, and diagnostics. Minor gaps exist around explicit navigation/history controls such as back, forward, or direct URL navigation separate from browser_open, but core workflows are covered.