Skip to main content
Glama
mikebeaton

Chrome Dialog MCP

by mikebeaton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Chrome Dialog MCP

No user-submitted related servers found.

    Related Servers

    • DynamicAgent2UI

      iorcunyilmaz
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to render native-looking floating dialogs and forms on the user's desktop, capturing user interactions like button clicks and form inputs.
      -

    • windows2text

      ArronHC
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Windows UI Automation screen-to-text and computer-use via MCP, allowing agents to observe, decide, and act on Windows applications through accessibility data without OCR.
      MIT

    • win-dialog-mcp

      tigersaint88-app
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to semantically discover and operate Windows dialogs — waiting for, listing, describing and reading dialog controls, clicking buttons by Chinese/English labels, filling fields, and completing Save As, Open and MessageBox flows, with UIA fallback for non-standard WPF/WinUI/Electron dialogs. Actions are intent-based rather than coordinate-based, with configurable timeouts and text hashed in logs for privacy.
      MIT

    • win-pilot

      JeremyWangCY
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Windows agents to control desktop applications and isolated Chromium sessions through a unified computer tool, supporting discovery, observation, input, window management, browser automation, and sequencing actions.
      570 npm
      1
      MIT

    • human-loop-mcp

      dzulfiikar
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to ask human operators questions through polished browser dialogs, supporting text/choice/confirmation inputs and file attachments.
      7
      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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct role in the dialog-handling lifecycle: launch, check status, arm capture, retrieve captured dialog, respond, and close. The main potential overlap is between get_dialog_status and get_captured_dialog, but the descriptions clearly separate status-only reporting from consuming a capture interval and returning an ID. Minor ambiguity remains because launch_chrome's lengthy description references other tools and workflows, which could distract an agent from the tool's core purpose.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: launch_chrome, get_dialog_status, start_dialog_capture, get_captured_dialog, respond_to_dialog, close_chrome. The verbs are clear and the noun phrases are predictable, even though the ordering of qualifiers varies slightly (e.g., dialog_status vs captured_dialog).

    Tool Count5/5

    Six tools is well-scoped for the server's purpose of managing Chrome native dialogs. Each tool corresponds to a necessary step in the workflow: session launch, status check, capture arming, dialog retrieval, response, and cleanup. No tool appears redundant or trivial.

    Completeness4/5

    The lifecycle is largely complete: create a session, check state, arm capture, retrieve an anticipated dialog, respond securely, and close the session. Minor gaps exist, such as no explicit tool to cancel an armed capture without consuming it, no way to list active sessions, and no dedicated reconnect operation beyond launch_chrome with a token. These are workarounds, but the core dialog-handling flow is covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources