hyper-playwright
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --cdp | No | Attach to a running browser, specified as a URL or port. | |
| --port | No | HTTP port for --transport http. | 8787 |
| --headed | No | Show the browser window. | off |
| --browser | No | Browser to use: chrome, msedge or chromium. | auto |
| --profile | No | Persistent browser profile directory. | ~/.hyper-playwright/profile |
| --max-tabs | No | Number of concurrent swarm tabs (1–3). | 3 |
| --transport | No | Transport to use: stdio or http. | stdio |
| --allow-media | No | Stop blocking images, fonts and media. | off |
| --allow-file-urls | No | Permit file:// navigation. | off |
| --allow-write-anywhere | No | Permit browser_export_test to write outside the working directory or a temp directory. | off |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Fast browser control. browser_navigate returns compact Semantic Markdown with [eN] references; act on those references with browser_batch; use browser_swarm for multiple URLs at once.
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 |
|---|---|
| browser_navigateA | Open a URL in the browser, wait for the page to settle, then return a compact Semantic Markdown snapshot. Interactive elements are listed with stable [eN] references (e.g. "[e12] Search (button)"). Use those references with browser_batch to act on the page. Ads, trackers and heavy media are blocked by default. |
| browser_batchA | Execute several actions on the current page in one turn. Fill/check/hover/type/focus run in PARALLEL with cloned multi-cursors; everything else runs SEQUENTIALLY because it can change the page. Drag takes a destination ref in "value" (e.g. value "e8"); upload takes file path(s); reload/back/forward/dialogAccept/dialogDismiss take no ref. Returns a per-action report, obstacle diagnostics for failed clicks, and a compact "+ / -" diff. |
| browser_swarmA | Open several URLs concurrently across a pool of up to 3 recycled worker tabs (max 2 per domain) and return one merged Markdown report. Use this instead of sequential navigations when a task spans multiple pages, lists or links. Each task can carry a "query" to scope the extracted content. |
| browser_snapshotA | Re-distil the current page and return a fresh Semantic Markdown snapshot with updated [eN] references. Also able to capture a PNG screenshot (useful for applications or vision workflows). |
| browser_debugA | Return buffered console errors, uncaught page errors and failed network requests collected since the browser started. Use this when a page renders incorrectly or an action fails for an unknown reason. |
| browser_export_testA | Convert every action performed in this session into a runnable @playwright/test spec file, using role+name locators so the test survives re-renders. Returns the file contents, and optionally writes them to disk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct phase of browser automation: navigate (single URL), swarm (multi-URL), batch (actions), snapshot (refresh state), debug (diagnostics), export_test (test generation). The only mild overlap is navigate vs. swarm, but the descriptions clearly separate one-page from many-page use.
All names share the browser_ prefix and snake_case, so the family is obvious. There is a slight mix of noun-style labels (snapshot, batch, swarm) with verb-style ones (navigate, debug), but the pattern stays readable and predictable.
Six tools cover the whole browse-act-inspect-export loop without filler. Each has a clear role, and no operation feels redundant or missing from the set.
Navigation, batched interaction, state refresh, diagnostics, multi-page scraping and test export give near-full lifecycle coverage. Minor gaps exist, such as explicit session/tab cleanup or a standalone screenshot/download control, but snapshot's PNG option and batch actions cover most needs.