superpowers-chrome
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISPLAY | No | For Linux/WSL2 headed mode, set DISPLAY environment variable (e.g., ':0') | |
| CHROME_WS_HOST | No | Override host for DevTools traffic (default 127.0.0.1) | |
| CHROME_WS_PORT | No | Override port for Chrome DevTools (default dynamically allocated from range 9222-12111) | |
| CHROME_EXTRA_ARGS | No | Whitespace-separated list of additional Chrome flags (e.g., '--use-gl=angle --use-angle=swiftshader-webgl') | |
| CHROME_WS_PROFILE | No | Set 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| use_browserA | Control persistent Chrome browser with automatic page capture. Every DOM action (navigate, click, type, select, eval) auto-captures to the session dir:
Prefer reading these files to using 'extract' or 'screenshot' whenever possible. 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/obra/superpowers-chrome'
If you have feedback or need assistance with the MCP directory API, please join our Discord server