Skip to main content
Glama
ohaoz

Codex Chrome MCP

by ohaoz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Codex Chrome MCP

No user-submitted related servers found.

    Related Servers

    • Chrome MCP

      hmumu230-ops
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a live Chrome browser to any MCP client through a single local endpoint, enabling real-tab control, DOM interaction, cookies and session use, network/console capture, PDF export, and CDP-powered debugging.
      MIT

    • octolimb

      kaleemibnanwar
      A
      license
      A
      quality
      C
      maintenance
      Enables any MCP-capable agent to drive a real Chrome browser through stdio or HTTP, supporting navigation, page reading, interaction, scrolling, JavaScript execution, and replaying saved step-by-step recipes.
      24
      Apache 2.0

    • Remote Browser

      syntropika
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive a live, persistent self-hosted Chromium session over MCP, running browser actions via Playwright/CDP, capturing page snapshots, screenshots and videos, and managing uploads and downloads in the same tabs and signed-in accounts a human user can take over at any time.
      18 npm
      Apache 2.0

    • kilogent-browser

      codebridger
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.
      1
      Apache 2.0
    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

    A3.5/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools are clearly distinct: navigation, interaction, CDP, session management. However, browser documentation, browser_exec, and eval_js have some overlap in the 'run code against browser' space, and list_user_tabs vs list_tabs are subtly different but well-explained. The click/type_text/press_key/scroll interaction tools are well-differentiated.

    Naming Consistency3/5

    There's a mix of conventions: some verb_noun pairs (list_user_tabs, claim_tab, type_text, press_key, fetch_url), some bare verbs (goto, scroll, click, snapshot), and a few camelCase (browser_exec, eval_js, cdp_send, cdp_events). The underscore convention dominates but lacks a uniform verb_noun pattern; the presence of camelCase tools (browser_exec, eval_js, cdp_events) breaks consistency.

    Tool Count4/5

    20 tools is on the higher end but justifiable for a browser automation surface covering navigation, interaction, inspection, DOM access, network fetching, CDP, and session lifecycle. Each tool fills a genuine niche, though some (cdp_send/cdp_events, browser_exec/eval_js) overlap and could arguably be consolidated.

    Completeness4/5

    The surface covers the full browser automation lifecycle: tab management (new/claim/list), navigation (goto), inspection (snapshot, screenshot, console logs), interaction (click, type, keys, scroll), DOM/JS access (eval_js, browser_exec), network (fetch_url), and cleanup (finalize). Minor gaps include no explicit form-submit or file-upload helper, and no tool to close a single specific tab rather than all via finalize, but these are workable via browser_exec.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources