Skip to main content
Glama
obra

superpowers-chrome

by obra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to superpowers-chrome

No user-submitted related servers found.

    Related Servers

    • BrowserUse

      YisRime
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to control Chrome/Edge browsers via CDP, including page navigation, element interaction, snapshots, network debugging, script execution, and performance tracing.
      AGPL 3.0

    • Servo MCP

      gptenv
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables controlling isolated headless browser sessions through MCP tools for navigation, inspection, JavaScript evaluation, input actions, screenshots, and multi-tab session management.
      16 npm
      1
      MIT

    • Chrome DevTools MCP

      josh6011
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets coding agents control and inspect a live Chrome browser for reliable automation, in-depth debugging, and performance analysis. Provides access to Chrome DevTools capabilities such as tracing, network inspection, screenshots, and console messages through MCP clients.
      1,737,496 npm
      Apache 2.0
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only a single tool, so there is no possibility of confusing it with another tool on this server. All routing between operations happens through the documented 'action' parameter rather than through tool selection, which removes cross-tool misselection entirely.

    Naming Consistency4/5

    The lone name 'use_browser' follows a clean verb_noun convention. With only one tool there is no pattern to break, so consistency is trivially satisfied, though the naming dimension is largely uninformative here.

    Tool Count3/5

    A single tool for the whole browser-control domain is on the thin side of appropriate, pushing a large multi-action surface (navigate, click, type, select, eval, tabs, captures) into one dispatcher. It works as a pattern but makes discovery and schema validation harder than a small set of focused tools.

    Completeness4/5

    The action set appears to cover the core browser lifecycle: navigation, DOM interaction, eval, tab management, and automatic capture artifacts, plus a help action for discovering payload shapes. Minor gaps (explicit wait-for-condition, network interception, download/upload handling) are largely workable via eval.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources