P
pourdev/pour-cli
Audit any URL against WCAG 2.2 from your terminal, powered by the
updated 2026-11-14
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · pourdev/pour-cli · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
pourdev/pour-cli;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# pour-cli
Excerpted from the repository README (abridged)
Audit any URL against WCAG 2.2 from your terminal, powered by the
pour engine: a clean-room WCAG
engine written from the W3C specifications, the same engine behind
pour.dev.
sh
npm install -g pour-cli
pour example.com
The page is loaded in headless Chrome, the engine runs against the live DOM,
and the findings land on stdout: rule, severity, WCAG success criterion, the
exact failing elements as CSS paths, and what to fix. Findings the engine
cannot judge conclusively are reported as "needs review" rather than guessed
at, and the exit code makes it a CI gate out of the box.
## Requirements
Node 18+, and an installed Chrome (or Chromium, or Edge). The CLI drives the
browser you already have via puppeteer-core, so installing it never
downloads one. Point --browser (or PUPPETEER_EXECUTABLE_PATH) at a
binary to use something else.
## Usage
pour [options] one page
pour report [options] a site, or a list of domains (see below)
pour check files on disk, no browser (see below)
pour mcp browser tools for an AI agent (see below)
pour skill [install] teach a coding agent to use pour (see below)
One page
--viewport WxH viewport (default 1440x900); a bare width implies x900
--scroll scroll through the page before auditing (lazy content)
--wait extra settle delay after load (default 0)
--timeout navigation timeout (default 30000)
--exclude CSS selector excluded from every rule
--bp include best-practice rules alongside WCAG A+AA
--root with a local .html file: the folder served as the site
root, for assets addressed from there (/css/site.css);
default the file's own folder
Output
--format terminal (default) | json | markdown (a pull-request
comment); pour check adds github (annotations on the
changed lines) and sarif (GitHub code scanning)
--level quiet (the totals line) | rules (one line per rule) |
max (default: everything)
--max-nodes element details shown per rule (default 5, 0 = all)
--json the full engine results as JSON
--fail-on violations (default) | incomplete | none
Screenshots
--filter screenshot the page through a vision/sensory simulation
instead of auditing (--filter list shows them all)
--shot [file] save a PNG (default name from the URL and filter);
no audit runs
--full the full page height, not just the viewport
Signed-in sites (pour and pour report)
--login a browser window opens at the address; sign in there,
press Enter here, and the run continues signed in.
The session lives in memory for this run only:
nothing is written to disk
--basic user:pass HTTP authentication (a staging site behind a wall),
the one thing a sign-in window cannot hand over
Browser
--browser Chrome/Chromium binary to drive
--headful run the browser with a visible window
--insecure ignore TLS certificate errors
Exit codes: 0 clean, 1 findings (per --fail-on), 2 error.
A scheme-less URL is tried over https first and falls back to http when the
TLS handshake fails, the same way a browser address bar behaves.
## Vision simulations
--filter renders the page as someone with a particular vision or sensory
condition experiences it and saves the result as a PNG:
sh
pour example.com --filter deuteranopia
pour example.com --filter glaucoma --shot tunnel.png
pour --filter list
pour engine: a clean-room WCAG
engine written from the W3C specifications, the same engine behind
pour.dev.
sh
npm install -g pour-cli
pour example.com
The page is loaded in headless Chrome, the engine runs against the live DOM,
and the findings land on stdout: rule, severity, WCAG success criterion, the
exact failing elements as CSS paths, and what to fix. Findings the engine
cannot judge conclusively are reported as "needs review" rather than guessed
at, and the exit code makes it a CI gate out of the box.
## Requirements
Node 18+, and an installed Chrome (or Chromium, or Edge). The CLI drives the
browser you already have via puppeteer-core, so installing it never
downloads one. Point --browser (or PUPPETEER_EXECUTABLE_PATH) at a
binary to use something else.
## Usage
pour [options] one page
pour report [options] a site, or a list of domains (see below)
pour check files on disk, no browser (see below)
pour mcp browser tools for an AI agent (see below)
pour skill [install] teach a coding agent to use pour (see below)
One page
--viewport WxH viewport (default 1440x900); a bare width implies x900
--scroll scroll through the page before auditing (lazy content)
--wait extra settle delay after load (default 0)
--timeout navigation timeout (default 30000)
--exclude CSS selector excluded from every rule
--bp include best-practice rules alongside WCAG A+AA
--root with a local .html file: the folder served as the site
root, for assets addressed from there (/css/site.css);
default the file's own folder
Output
--format terminal (default) | json | markdown (a pull-request
comment); pour check adds github (annotations on the
changed lines) and sarif (GitHub code scanning)
--level quiet (the totals line) | rules (one line per rule) |
max (default: everything)
--max-nodes element details shown per rule (default 5, 0 = all)
--json the full engine results as JSON
--fail-on violations (default) | incomplete | none
Screenshots
--filter screenshot the page through a vision/sensory simulation
instead of auditing (--filter list shows them all)
--shot [file] save a PNG (default name from the URL and filter);
no audit runs
--full the full page height, not just the viewport
Signed-in sites (pour and pour report)
--login a browser window opens at the address; sign in there,
press Enter here, and the run continues signed in.
The session lives in memory for this run only:
nothing is written to disk
--basic user:pass HTTP authentication (a staging site behind a wall),
the one thing a sign-in window cannot hand over
Browser
--browser Chrome/Chromium binary to drive
--headful run the browser with a visible window
--insecure ignore TLS certificate errors
Exit codes: 0 clean, 1 findings (per --fail-on), 2 error.
A scheme-less URL is tried over https first and falls back to http when the
TLS handshake fails, the same way a browser address bar behaves.
## Vision simulations
--filter renders the page as someone with a particular vision or sensory
condition experiences it and saves the result as a PNG:
sh
pour example.com --filter deuteranopia
pour example.com --filter glaucoma --shot tunnel.png
pour --filter list
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/pourdev-pour-cli/)
- Source
- awesome · https://github.com/pourdev/pour-cli
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.