Asklear Browser MCP
OfficialRelated Servers
Alternatives to Asklear Browser MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceStandalone browser automation MCP server supporting both BrowserOS and standard Chrome. Enables 16 MCP tools for browser control including navigation, interaction, and content extraction.15 npm-
- AlicenseNot gradedqualityBmaintenanceEnables 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.32 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
- AlicenseAqualityAmaintenanceMCP server that drives your real Chrome/Edge/Opera browser through a Chrome extension and DevTools Protocol, preserving logins and session state, and can also perform OS-level mouse and keyboard input behind approval.5121 PyPI2MIT
- AlicenseNot gradedqualityCmaintenanceLocal browser automation MCP server for Claude Code, enabling navigation, clicking, typing, and inspecting real web pages via Google Chrome.19 npm1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceAn extension-based MCP server that enables AI assistants to control your existing Chrome browser, leveraging your active login states and settings for automation. It provides over 20 tools for tasks like semantic tab search, screen capture, network monitoring, and direct element interaction.-
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.