Skip to main content
Glama
Jmsa

argus

by Jmsa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to argus

No user-submitted related servers found.

    Related Servers

    • paparazzi

      nicksenap
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.
      2 npm
      2
      MIT

    • Chrome Tools MCP Server

      nicholmikey
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for interacting with Chrome through its DevTools Protocol, enabling remote control of Chrome tabs to execute JavaScript, capture screenshots, monitor network traffic, and more.
      91 npm
      52
      MIT

    • mcp-chromium-cdp

      duquesnay
      A
      license
      A
      quality
      D
      maintenance
      MCP server for controlling Chromium/Chrome via Chrome DevTools Protocol. Supports cross-platform automation, auto-launch, and automatic reconnection.
      25
      1
      MIT

    • Puppeteer Debugger MCP Server

      ALIEX7664
      A
      license
      B
      quality
      C
      maintenance
      An MCP server based on Puppeteer and Chrome DevTools Protocol for advanced browser debugging, performance analysis, and memory detection. It enables users to inspect DOM elements, monitor console errors, capture screenshots, and perform heap snapshot analysis through persistent browser connections.
      10
      8 npm
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 32 tools

    Disambiguation5/5

    Each tool is namespaced by subsystem (browser, tab, page, dom, network, console, banner) and performs a clearly distinct action. Even similar tools like network_remove_mock versus network_clear_mocks are easily differentiated by specificity.

    Naming Consistency4/5

    The naming is largely consistent with a domain_prefix plus action pattern, and all tools use snake_case. Minor deviations like browser_status, tab_screenshot, and dom_input_value break the strict verb_noun pattern but do not cause real confusion.

    Tool Count2/5

    With 32 tools, the server exceeds the 25-tool threshold and feels heavy even though the tools are organized by subsystem. The count is defensible for a full browser automation surface, but it is still more than a typical MCP server should expose.

    Completeness3/5

    The toolset covers core browser automation workflows: browser lifecycle, tabs, DOM interaction, network interception, console logging, and screenshots. However, browser_launch has no corresponding browser_close or quit tool, so a launched Chrome instance cannot be cleanly terminated through the server.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources