Skip to main content
Glama
masterdeepak15

chrome-control-mcp

by masterdeepak15
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to chrome-control-mcp

No user-submitted related servers found.

    Related Servers

    • chrome-mcp

      Mehmoodqureshi
      A
      license
      B
      quality
      A
      maintenance
      Enables controlling a real Chrome browser from MCP hosts like Claude, with extension-based or CDP fallback, supporting tabs, navigation, interaction, and page reading tools.
      20
      464 npm
      6
      MIT

    • Claude Chrome MCP

      nonsleepr
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation through the Claude Chrome Extension, allowing agents to navigate websites, fill forms, take screenshots, and debug web apps via standard MCP protocols.
      1
      MIT

    • cc-chrome

      joshoq
      A
      license
      B
      quality
      C
      maintenance
      Enables browser control through your existing signed-in Chrome profile, letting MCP clients like Claude Code manage tabs, navigate, inspect pages, and perform real user interactions via tool calls. Works with any model backend without needing Playwright or a fresh browser profile.
      21
      MIT

    • Controlium

      am-will
      A
      license
      Not graded
      quality
      B
      maintenance
      Chrome extension + MCP bridge that gives Claude control over your real browser via CDP, enabling navigation, clicking, typing, scrolling, screenshots, and JS execution with a visible cursor and tab-bring-to-front.
      1
      MIT

    • browser-mcp

      747486675
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to control a real, visible Chrome via MCP for navigating, clicking, typing, downloading files, and reading page content. Supports isolated CDP and everyday-Chrome extension modes with user confirmations for risky actions.
      21 npm
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    C2.9/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (element click vs coordinate click, page snapshots vs screenshots, console vs network listings). A few pairs overlap enough to risk misselection: fill vs type_text vs fill_form, and the three performance_* tools share a narrow domain. Descriptions do clarify these boundaries, so misselection is unlikely but possible.

    Naming Consistency4/5

    The set mostly follows a consistent snake_case verb_noun convention (navigate_page, take_snapshot, click_at, list_pages). Deviations like 'status' (noun without verb), 'cdp' (bare acronym), and 'emulate' (verb without object) are minor and still readable. No mixed camelCase/snake_case confusion.

    Tool Count2/5

    At 32 tools this server is well above the typical well-scoped range and feels heavy for browser control. Several capabilities could be consolidated (performance_start/stop/analyze_insight, take_heapsnapshot, cdp) or are only occasionally needed. The count increases selection burden without proportional unique value.

    Completeness4/5

    The surface covers the core browser-automation lifecycle well: navigation, element interaction, page management, and diagnostics (console, network, performance, heap). Minor gaps exist around cookie/local-storage management and download handling, but these can be worked around via evaluate_script or cdp. No dead ends for common workflows.

    Resources