Skip to main content
Glama
Asklear

Asklear Browser MCP

Official
by Asklear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Asklear Browser MCP

No user-submitted related servers found.

    Related Servers

    • browseros-mcp

      dreamsxin
      F
      license
      Not graded
      quality
      B
      maintenance
      Standalone browser automation MCP server supporting both BrowserOS and standard Chrome. Enables 16 MCP tools for browser control including navigation, interaction, and content extraction.
      8 npm
      -

    • deeporax-browser-mcp

      imfaisii
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP 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

    • agent-browser-mcp

      LinVireo
      A
      license
      B
      quality
      A
      maintenance
      MCP 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.
      55
      2
      MIT

    • browser-mcp

      ruggieroromulo
      A
      license
      Not graded
      quality
      C
      maintenance
      Local browser automation MCP server for Claude Code, enabling navigation, clicking, typing, and inspecting real web pages via Google Chrome.
      18 npm
      1
      MIT

    • Chrome MCP Server

      davincinewton
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      An 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.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    All six tools follow the exact same single-word lowercase verb pattern. This is fully consistent and easy to predict.

    Tool Count5/5

    Six tools is a well-scoped size for a browser automation server. Each tool covers a core interaction or observation action without unnecessary bloat.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources