Skip to main content
Glama
335234131

agent-browser-mcp

by 335234131
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agent-browser-mcp

No user-submitted related servers found.

    Related Servers

    • chrome-agent-browser

      oscs1024-pixel
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to directly operate a user's local Chrome browser with full login state and cookies, supporting 23 tools such as tab management, clicking, typing, screenshots, file upload, and network inspection through natural language.
      MIT

    • chrome-agent-mcp

      otaviosenne
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to fully control Google Chrome: navigate, click, fill forms, inspect DevTools, and manage tabs with parallel execution and session isolation.
      24
      7 npm
      MIT

    • Chrome MCP Server

      femto
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control and automate your Chrome browser directly, leveraging existing login states and configurations for tasks like content analysis, semantic search across tabs, screenshots, network monitoring, and interactive operations.
      10
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some overlap exists: 'capture_desktop_screenshot' and 'capture_page_screenshot' could be confused for similar screenshot tasks, and 'cdp_batch' and 'cdp_command' both handle CDP commands with subtle differences. The descriptions help clarify, but an agent might occasionally misselect between these pairs.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, such as 'capture_desktop_screenshot', 'list_tabs', and 'open_new_tab'. This predictability makes it easy for agents to understand and use the tools without confusion from mixed naming conventions.

    Tool Count4/5

    With 20 tools, the count is slightly high but reasonable for a browser automation server that covers desktop interaction, CDP commands, and page management. It feels comprehensive without being overly bloated, though it borders on the upper limit of typical scoping.

    Completeness5/5

    The tool set provides complete coverage for browser automation, including navigation, tab management, input simulation, screenshot capture, CDP access, and diagnostics. There are no obvious gaps; agents can perform core workflows like opening URLs, interacting with pages, and debugging without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources