Skip to main content
Glama
obra

superpowers-chrome

by obra

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DISPLAYNoFor Linux/WSL2 headed mode, set DISPLAY environment variable (e.g., ':0')
CHROME_WS_HOSTNoOverride host for DevTools traffic (default 127.0.0.1)
CHROME_WS_PORTNoOverride port for Chrome DevTools (default dynamically allocated from range 9222-12111)
CHROME_EXTRA_ARGSNoWhitespace-separated list of additional Chrome flags (e.g., '--use-gl=angle --use-angle=swiftshader-webgl')
CHROME_WS_PROFILENoSet a fixed profile name to share Chrome between processes

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
use_browserA

Control persistent Chrome browser with automatic page capture.

Every DOM action (navigate, click, type, select, eval) auto-captures to the session dir:

  • {prefix}.png — viewport screenshot

  • {prefix}.md — page content as structured markdown

  • {prefix}.html — full rendered DOM

  • {prefix}-console.txt — browser console messages

Prefer reading these files to using 'extract' or 'screenshot' whenever possible. Actions on a page showing token-shaped content (Slack/GitHub/1Password tokens, otpauth:// URIs) or any data-sen-secret element write no capture files, token-shaped values are redacted from all output, and eval refuses outright while any data-sen-secret element is on the page — an accident guard against a cooperating agent's own reads, not a security boundary. A secret with no distinctive shape (bare TOTP seed, backup code) is captured like any other text until it is marked: mark it with 'set_attr' name 'data-sen-secret' as soon as the action that revealed it returns, before any other action on that page. Capture files written before the mark keep the value and are not deleted, so don't read them back. 'set_attr' is a write-only setter for exactly 'data-sen-nonce' or 'data-sen-secret' that is exempt from that eval restriction (see 'help' for details) — use it, not eval, to write onto the page while a secret is present.

Schema: 4 parameters — action, selector (CSS/XPath or null), payload (string or object), timeout (ms). selector targets a DOM element (null/omit for navigation, eval, tab management, etc.). payload is a string for simple actions (navigate=URL, type=text, eval=JS, keyboard_press=key). payload is an object for structured actions (set_viewport={width,height}, drag_drop={target}, etc.) — a JSON-encoded string of the same object works too. Tabs are tracked as sticky state; use switch_tab to change the active tab. Use action='help' for full per-action payload shapes.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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