Skip to main content
Glama
argon-bridge-9router

argon-bridge-9router

by faizalzn

Related Servers

Alternatives to argon-bridge-9router

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants and CLI clients to run deep-reasoning prompts against Google AI Studio's Gemini 4 Argon model through an authenticated real-browser CDP session, with file attachments, persistent sessions, and shared browser access.
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables autonomous coding agents and Antigravity workflows to query Google’s 4 Argon reasoning model with configurable thinking depth, automatic multi-account failover, live quota tracking, and workspace-isolated conversation memory.
      44
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation and testing using Playwright through the Model Context Protocol.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation via the Model Context Protocol, supporting headless Playwright and extension bridges for controlling existing Chrome and Firefox tabs.
      8,154 npm
      ISC

    TDQS

    B3.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool on the server, so there is nothing for an agent to confuse it with. Its purpose (proxying a prompt to a chosen provider/model) is stated explicitly.

    Naming Consistency4/5

    The single name uses snake_case and a clear verb ('ask_'), but it redundantly bakes in the server/bridge name and a provider ('argon_playwright_9router'), making it long and vendor-specific. With only one tool there is no cross-tool pattern to break.

    Tool Count2/5

    A router spanning many providers/models plus a Playwright web bridge is a lot of surface compressed into one opaque passthrough tool. There is no way to discover providers/models or check bridge health without invoking the single call.

    Completeness2/5

    The core 'send a prompt' operation exists, but the obvious lifecycle around it is missing: listing available providers/models/combos, checking bridge or session status, and any error/retry or cancellation path. Agents are left with a single fire-and-hope entry point.