Skip to main content
Glama
q35888

agentic-browser-mcp

by q35888
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to agentic-browser-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-browser

      souhailmerroun-recyclebin
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Playwright browser automation as MCP tools, enabling AI assistants to control a real browser tab-by-tab for form filling, navigation, and more, while preserving the user's active session.
      -

    • sa2web-mcp

      sa2web
      A
      license
      C
      quality
      B
      maintenance
      Exposes a remote browser as MCP tools via Playwright, enabling AI agents to navigate and interact with web pages through DOM snapshots, clicks, typing, and form operations.
      40
      3 npm
      8
      Apache 2.0

    • monkeysee

      juliocesar
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.
      4 npm
      1
      MIT

    • browser-mcp-lab

      ashu0729will
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables browser automation through MCP, providing tools for navigation, interaction, page inspection, and form handling via a pinned Playwright MCP server.
      1
      MIT
    • orchords-web-pilot by ORCHORDS

      orchords-web-pilotofficial

      ORCHORDS
      F
      license
      A
      quality
      B
      maintenance
      Enables coding agents to drive a real Playwright-backed browser session, navigating, observing, interacting, and capturing proof on web pages via MCP tools across stdio and Streamable HTTP transports.
      15
      2
      -
    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

    A3.7/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct action or data source (click, type, navigate, eval, etc.), with no overlapping purposes. Descriptions clearly differentiate between similar actions like clicking vs. typing and reading console vs. storage.

    Naming Consistency4/5

    All tools use the 'browser_' prefix and snake_case, with most following a verb pattern (click, type, navigate). The tool 'browser_session' uses a noun instead of a verb, which is a minor inconsistency but still predictable.

    Tool Count5/5

    With 11 tools, the set covers all core browser automation tasks without unnecessary redundancy. The count is well-scoped for a comprehensive yet focused server.

    Completeness4/5

    The tool set covers primary browser interactions: navigation, clicking, typing, reading console/storage/eval, screenshots, session management, and manual intervention. Missing features like back/forward navigation or alert handling are minor gaps but do not severely hinder typical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources