Skip to main content
Glama
Sign In
otaviosenne

chrome-agent-mcp

by otaviosenne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to chrome-agent-mcp

No user-submitted related servers found.

    Related Servers

    • agent-browser-mcp

      335234131
      A
      license
      B
      quality
      F
      maintenance
      Enables AI agents to directly control your real Chrome browser with full context including login sessions, cookies, and open tabs. It provides tools for page scanning, JavaScript execution, CDP control, screenshots, and physical mouse/keyboard input for authentic browser automation.
      20
      245
      MIT

    • BrowserPilot

      cxcboss
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control a Chrome browser through natural language, supporting navigation, interaction, tab management, and data extraction.
      MIT

    • agentic-browser

      davarion-tech
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to control your installed Google Chrome through MCP or HTTP using compact text snapshots, exact pixel coordinates, and a visible cursor. It provides browser tools for navigation, clicking, typing, scrolling, tabs, forms, waiting, recording, and human handoff.
      35
      608 npm
      3
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.4/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools are clearly distinct action primitives (click, type, scroll, navigate, etc.), but there is overlap among browser_tabs, chrome_windows, and chrome_focus around tab/window switching. browser_snapshot and devtools_elements both expose page structure, though one is interaction-oriented and the other is inspection-oriented.

    Naming Consistency4/5

    The tool names mostly follow a clear browser_<verb>, devtools_<panel>, or chrome_<noun> pattern, which makes the set predictable. browser_tabs is a noun-based multi-action tool rather than a verb-noun name, and session_sync breaks the prefix convention.

    Tool Count3/5

    24 tools covers a broad browser-automation surface, but it is on the heavy end and includes very granular actions like navigate_back and navigate_forward that could have been combined. The count is justified by the inclusion of devtools and window management, yet it feels more like a toolkit than a focused MCP server.

    Completeness4/5

    The server covers core browser workflows well: tab lifecycle, navigation, page interaction, devtools inspection, storage, and window management. Minor gaps exist such as advanced network interception and drag-and-drop, but these can often be worked around with browser_evaluate.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources