Skip to main content
Glama
firyomaefx

Chrome MCP Control Center

by firyomaefx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Chrome MCP Control Center

No user-submitted related servers found.

    Related Servers

    • MCP Chrome Bridge

      wizardofweb125-lab
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control Chrome browser actions like navigation, clicking, form filling, screenshots, and console/network logging via an MCP server and Chrome extension.
      532 npm
      MIT

    • Chrome MCP Server

      davincinewton
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      An extension-based MCP server that enables AI assistants to control your existing Chrome browser, leveraging your active login states and settings for automation. It provides over 20 tools for tasks like semantic tab search, screen capture, network monitoring, and direct element interaction.
      -

    • Chrome MCP Server

      MNIsRed
      A
      license
      Not graded
      quality
      D
      maintenance
      An extension-based MCP server that enables AI assistants to control your browser, leveraging existing sessions and login states for automation and content analysis. It provides over 20 tools for semantic tab search, interactive element manipulation, and network monitoring directly within your daily Chrome environment.
      MIT

    • chrome-bridge

      kiarina
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets LLM agents control all Chrome browser tabs via accessibility snapshots, element references, and a virtual cursor, supporting operations like click, type, navigate, screenshot, and video recording.
      MIT

    • browser-mcp

      JuntongLiu96
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives coding agents full control over a real Chrome browser, enabling navigation, clicking, typing, screenshotting, and more via an MCP server and Chrome extension.
      9 npm
      2
      MIT
    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

    C2.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct action: waiting for a selector, clicking coordinates, and typing text. There is no overlap between their purposes.

    Naming Consistency4/5

    All tool names use snake_case, but the prefix differs ('browser_' vs 'computer_'). This minor inconsistency does not hinder readability.

    Tool Count3/5

    With only 3 tools, the server feels thin for a 'Chrome MCP Control Center'. It may be acceptable if the scope is intentionally narrow, but more tools are expected.

    Completeness2/5

    The tool set misses essential browser operations like navigation, page evaluation, or screenshot. For a control center, this leaves significant gaps that agents cannot work around.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources