Asklear Browser MCP
OfficialRelated Servers
Alternatives to Asklear Browser MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceStandalone browser automation MCP server supporting both BrowserOS and standard Chrome. Enables 16 MCP tools for browser control including navigation, interaction, and content extraction.6 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables local Chrome control for AI clients over MCP stdio, HTTP, or CLI, exposing 20 tools to extract page text, number and click elements, type text, scroll, manage tabs, capture screenshots, and bind uploaded files to file inputs. Operations run entirely on the local machine with origin allowlists and refusal of untrusted URLs, without calling a cloud model or consuming model tokens.37 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server to control a real Chrome browser from Claude, enabling navigation, DOM snapshots, clicks, typing, screenshots, and JS execution via a Chrome extension bridge.MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's real, already-logged-in Chrome — reading pages, clicking, typing, uploading files, taking screenshots, and inspecting tabs, cookies, console, and network traffic — via 25 browser automation tools that pass bot detection without a debugging port. Requires a companion Chrome extension and stays entirely on the user's machine.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that enables AI coding tools to drive the user's real, already-logged-in Chrome browser — reading pages, clicking, typing, navigating tabs, screenshots, and cookie, network, and storage access — without opening a remote-debugging port.1 npmISC
TDQS
Scored across 6 tools
Each tool name maps to a distinct browser action: navigate, click, fill, scroll, observe, and extract are mostly unambiguous. There is minor potential overlap between observe and extract since both involve reading page state, but their names and typical usage in browser automation are distinguishable.
All six tools follow the exact same single-word lowercase verb pattern. This is fully consistent and easy to predict.
Six tools is a well-scoped size for a browser automation server. Each tool covers a core interaction or observation action without unnecessary bloat.
The toolset covers the main browser workflow: navigate, observe/extract, click, fill, and scroll. Minor gaps such as explicit wait, back/forward navigation, reload, hover, or select operations are missing, but agents can work around most of these for common tasks.