SiteLint Auditor MCP
OfficialRun SiteLint audits and runtime issue collection through an MCP server.
Audit live URLs for WCAG accessibility, SEO, performance, and security, with optional filters for standards, audit types, WCAG levels/versions/criteria, and page-load wait behavior.
Audit raw HTML snippets with required filter arrays and configurable
waitUntil.Check a single WCAG success criterion on a URL and get pass/fail with violation count.
Capture runtime issues from a live page offline, including JS errors, network failures, console errors/warnings, resource errors, browser reports, page-load metrics, and user events, using selectable collectors.
List and retrieve detailed runtime issues for a site token, including stack traces, steps-to-reproduce event logs, network context, and console tail.
Access audit resources such as supported WCAG criteria and full JSON reports from prior audits.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SiteLint Auditor MCP Audit https://example.com for WCAG 2.2 AA accessibility issues."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SiteLint Auditor MCP Server
MCP server that runs SiteLint Auditor - WCAG and SiteLint Best Practices for accessibility, SEO, performance, and security audits via LLM agents.
The auditor bundle additionally supports WebMCP: when enabled it registers in-page tools on document.modelContext, so browser agents can run and inspect audits directly on a live site without this server. See WebMCP (in-page tools).
Quick start
npx @sitelint/auditor-mcpRequires Chromium or Chrome. The MCP server automatically detects an installed system browser. If none is available, Puppeteer normally downloads Chrome during package installation; if that download was skipped, it downloads Chrome for Testing on the first audit. No browser path configuration is required.
Related MCP server: mcp-seo
Tools
audit_url
Audit a live URL.
{
"url": "https://example.com",
"standards": ["wcag"],
"auditTypes": ["accessibility"],
"wcagLevels": ["A", "AA"],
"wcagVersions": ["2.2"],
"wcagCriteria": []
}audit_html
Audit raw HTML without fetching a URL. Defaults to waitUntil: "load" so image-based rules (e.g. oversized images, size calculations) see fully loaded assets. A timeout guards against hanging external resources — if the load event never fires, the audit aborts with a clear error instead of hanging. Pass waitUntil: "domcontentloaded" to skip slow assets entirely.
All filter parameters are required — pass empty arrays to skip a filter.
WCAG audit:
{
"html": "<!DOCTYPE html><html>...</html>",
"standards": ["wcag"],
"auditTypes": ["accessibility"],
"wcagLevels": ["A", "AA"],
"wcagVersions": ["2.2"],
"wcagCriteria": ["1.1.1", "1.4.3"]
}SiteLint best practices (proprietary SEO, performance, security):
{
"html": "<!DOCTYPE html><html lang=\"en\"><head><title>Test</title></head><body></body></html>",
"standards": ["sitelint"],
"auditTypes": ["seo", "performance", "security"],
"wcagLevels": [],
"wcagVersions": [],
"wcagCriteria": []
}Full audit (everything):
{
"html": "<!DOCTYPE html><html>...</html>",
"standards": ["wcag", "sitelint"],
"auditTypes": ["accessibility", "performance", "security", "seo"],
"wcagLevels": ["A", "AA", "AAA"],
"wcagVersions": ["2.0", "2.1", "2.2"],
"wcagCriteria": []
}check_wcag_criterion
Check a single WCAG criterion against a URL.
{
"url": "https://example.com",
"criterion": "1.1.1"
}Returns pass/fail with violation count.
Filter parameters
Filters are ANDed — a rule must match every provided filter to run. On audit_url filters are optional (omit or pass empty arrays to skip). On audit_html all filter parameters are required — pass empty arrays to skip.
Parameter | Values | Example |
|
|
|
|
|
|
|
|
|
|
|
|
| WCAG criterion numbers |
|
Omit a parameter (or pass empty array) to skip that filter.
Runtime issues (errors, network failures, console errors)
SiteLint captures runtime issues from live pages — JS errors, failed network requests, console errors/warnings, failed resource loads, browser reports, and page-load thresholds. Each issue carries a user events log (clicks, scrolls, navigation) that reproduces the "steps to reproduce".
Tools
Tool | Purpose |
| Load a URL with Puppeteer, inject the auditor with collection enabled, wait, return captured issues inline. Works offline, no platform account needed. |
| List issues for a site token (paginated; supports |
| Full detail for one issue group: stack trace, user events log, network context. |
Typical agent workflow
Reproduce — open the page in your browser (or run
capture_page_issues), trigger the bug.Capture — issues are captured automatically (extension: while browsing; page-load injection: sent to the platform; bookmarklet: stored locally).
Query — ask your agent:
"List the issues for site token X" "Get the issue with fingerprint Y — show me the stack trace and steps to reproduce"
Fix — the agent reads the source file from the stack trace (
location.filename/sourceLocation), applies the fix, and confirms.
Example prompts
"List recent runtime issues for my site (token
abc123), filter bytype: network_failure""Get issue group
6453...— what were the steps to reproduce?""Capture issues from
https://example.com/checkoutand tell me what broke""The console shows a TypeError on the payment page. Find it in the issues and fix the source."
Notes
Issues are local-first: stored in the page (localStorage) unless explicitly sent to the platform. The extension stores them in the browser; the MCP server works fully offline.
Deduplication is by fingerprint (type + message + stack + source) — repeated occurrences increment
count, not new rows.The events log is capped at 30 entries per issue; console tail at 50 entries.
Resources
URI | Description |
| Supported WCAG criteria with levels |
| Full JSON report from a previous audit |
Configuration
Environment variables
Variable | Default | Description |
| Automatic detection | Optional custom Chromium/Chrome executable path |
|
| Max concurrent audit pages (hard cap) |
|
| Navigation/render timeout (ms) |
|
| Set |
|
|
|
|
| Port for SSE transport |
SSE / HTTP transport
Run the server over Streamable HTTP instead of stdio:
AUDITOR_TRANSPORT=sse AUDITOR_PORT=3100 npm startThe server listens on 127.0.0.1:3100 and accepts MCP requests via POST /. Host and Origin headers are validated (localhost only). Graceful shutdown on SIGINT/SIGTERM closes the browser and the HTTP server.
Client config:
{
"mcpServers": {
"sitelint-auditor": {
"url": "http://127.0.0.1:3100"
}
}
}CLI flags
auditor-mcp --bundle ./custom-bundle.js --timeout 60000 --headless falseFlag | Env equivalent |
|
|
|
|
|
|
|
|
| — |
|
|
|
|
Integration guides
opencode
Add to ~/.config/opencode/opencode.json:
{
"mcp": {
"sitelint-auditor": {
"type": "local",
"command": ["npx", "-y", "@sitelint/auditor-mcp"]
}
}
}For a local build:
{
"mcp": {
"sitelint-auditor": {
"type": "local",
"command": ["node", "/path/to/auditor-mcp/dist/cli.js"]
}
}
}With custom Chromium:
{
"mcp": {
"sitelint-auditor": {
"type": "local",
"command": ["npx", "-y", "@sitelint/auditor-mcp"],
"environment": {
"AUDITOR_BROWSER_PATH": "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome",
"AUDITOR_TIMEOUT": "60000"
}
}
}
}Claude Desktop
Edit claude_desktop_config.json:
{
"mcpServers": {
"sitelint-auditor": {
"command": "npx",
"args": ["-y", "@sitelint/auditor-mcp"]
}
}
}Claude Code
Plugin (recommended)
/plugin marketplace add sitelint/auditor-mcp
/plugin install auditor-mcp@sitelintManual
claude mcp add sitelint-auditor -- npx -y @sitelint/auditor-mcpCodex
Plugin (recommended)
codex plugin marketplace add sitelint/auditor-mcp
codex plugin add auditor-mcp@sitelintManual
codex mcp add sitelint-auditor -- npx -y @sitelint/auditor-mcpZCode
{
"sitelint-auditor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sitelint/auditor-mcp@latest"
]
}
}VS Code (Cline)
In Cline extension settings → MCP Servers:
{
"sitelint-auditor": {
"command": "npx",
"args": ["-y", "@sitelint/auditor-mcp"]
}
}VS Code (Continue)
In ~/.continue/config.json:
{
"experimental": {
"mcpServers": {
"sitelint-auditor": {
"command": "npx",
"args": ["-y", "@sitelint/auditor-mcp"]
}
}
}
}AnythingLLM
{
"mcpServers": {
"sitelint-auditor": {
"command": "npx",
"args": ["-y", "@sitelint/auditor-mcp"]
}
}
}Other MCP clients
Any MCP client can connect. Use stdio transport (default) for local tools, or AUDITOR_TRANSPORT=sse with AUDITOR_PORT=3100 for remote.
Build from source
git clone <repo>
cd auditor-mcp
npm install
npm run build
# Bundle the auditor engine
cp /path/to/auditor/dist/auditor.bundle.js vendor/
cp /path/to/auditor/app/translations/en-us.json vendor/translations/Requirements
Node.js 20+
Chromium or Chrome (detected automatically, or downloaded by Puppeteer during installation/on the first audit if needed)
SiteLint Auditor bundle (vendored as
vendor/auditor.bundle.js)
How it works
Launches headless Chromium via Puppeteer (single browser, pages capped by
AUDITOR_CONCURRENCY)Loads the target page and waits for it to settle (bounded by
AUDITOR_TIMEOUT)Injects the SiteLint Auditor JS bundle into the page
Runs a single-shot audit against the current DOM state
Formats results into a concise text report with grouping and truncation for long outputs
Stores full JSON as a resource accessible via
auditor://report/{id}
Navigation failures, timeouts, and browser-launch errors are returned as readable messages rather than raw exceptions.
Limitations vs. embedded auditor
When SiteLint Auditor is embedded directly into a website via <script>, it watches for DOM mutations, re-tests dynamically loaded content, and provides an interactive sidebar UI. The MCP server does not do any of that — it takes a one-time snapshot of the page at the moment of injection. Content loaded after the audit starts (lazy images, infinite scroll, SPA route transitions) is not evaluated. For SPAs or pages with heavy dynamic content, consider waiting for full render before calling the tool.
WebMCP (in-page tools)
WebMCP turns the page itself into a tool server: the site exposes client-side functions with JSON schemas, and a browser agent invokes them directly in the open tab. No stdio/SSE transport, no headless browser, no server deployment.
When the auditor is embedded via <script> with the webmcp option enabled, it registers:
Tool | Description |
| Runs a full audit of the live page; returns score and issue totals |
| Issues from the last audit with translated messages and element locators ( |
| All registered rules with id, severity, standard and WCAG level |
| Scrolls to and visually highlights the element for an issue |
Enabling from page code:
auditor.config({ webmcp: true });
auditor.run();The flag is opt-in and defaults to false. Registration is feature-detected: browsers without
document.modelContext silently skip it and the auditor behaves exactly as before.
When to use WebMCP instead of this server
Live page state — audits SPAs, authenticated views, and content rendered after load; the server only snapshots the initial DOM (see Limitations vs. embedded auditor above).
Fix-and-verify loop — the agent changes the page, re-runs
sitelint_run_audit, and usessitelint_highlight_issueto show the user what remains — all inside the user's tab.Assistive and browser-agent workflows — the agent and the user share one context.
Requirements
Chromium 146+ with WebMCP enabled (
chrome://flags/#enable-webmcp-testingin preview builds; Chrome 150+ exposes the producer API ondocument.modelContext)Secure context (HTTPS)
Tools are visible to same-origin consumers only; cross-origin exposure requires the
toolspermissions policy plusexposedToat registration
WebMCP complements this server rather than replacing it: headless audits of arbitrary URLs (CI,
batch checks, sites that do not embed the auditor) stay on @sitelint/auditor-mcp; in-browser
agents driving a live site use the WebMCP tools.
Available Tools
6 toolsaudit_htmlA
Audit raw HTML snippet against WCAG/SEO standards. Creates a sandbox page to analyze the markup.
Inputs: html (required), standards (required), auditTypes (required), wcagLevels (required), +3 more.
audit_urlA
Run a SiteLint audit on a live URL. Checks WCAG accessibility, SEO, performance, and security. Optionally filter by standard, audit type, WCAG level, version, or specific success criteria.
Inputs: url (required), standards, waitUntil, auditTypes, +3 more.
capture_page_issuesB
Load a page with Puppeteer, inject the SiteLint auditor with runtime issue collection enabled, wait, and return captured issues inline. No platform account required — works fully offline.
Inputs: url (required), waitMs, collectors.
check_wcag_criterionA
Check a single WCAG success criterion against a page. Filters audit to one criterion, level, and WCAG standard — faster than full audit. Returns pass/fail per element.
Inputs: url (required), criterion (required), level.
get_issueB
Get full detail for a single issue group: stack trace, user events log (steps to reproduce), network context, and console tail.
Inputs: groupId (required), siteApiToken (required).
list_issuesA
List recent runtime issues captured by the SiteLint auditor for a site. Returns trimmed fields (issueId, ts, type, severity, pageUrl, message, fingerprint, count). This is the "go find what I just hit" call.
Inputs: siteApiToken (required), limit, types, minutes, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Core issue tools list_issues/get_issue are clearly distinct retrieval levels, and audit_html/audit_url separate raw markup from live URL auditing. However, check_wcag_criterion overlaps heavily with audit_url's optional success-criteria filtering, and capture_page_issues vs audit_url both load pages, so an agent could sometimes hesitate between them.
All names use snake_case and a predictable verb_noun pattern: list_issues, get_issue, capture_page_issues, audit_html, audit_url, check_wcag_criterion. Singular/plural differences (get_issue vs list_issues) follow normal REST-like conventions.
Six tools is well-scoped for an auditing server, with each tool covering a distinct operation: retrieve issues, inspect issue detail, capture runtime issues, audit HTML, audit URL, and check one WCAG criterion. No obvious filler or missing bulk.
The surface covers issue discovery/detail, live page capture, HTML/URL audits, and single-criterion checks, which are the core operations for an auditor. Minor gaps exist around batch/multi-page auditing or listing available sites/audit history, but these are likely workable around.
Maintenance
Related MCP Connectors
Website health, SEO, security-header, SSL and broken-link audits for AI agents.
Audit public webpages and supplied markup for HTML, CSS, SEO, JSON-LD, and link issues.
Website QA for your coding agent: audit SEO, performance, security, accessibility over MCP.
Free technical-SEO audit MCP: crawl a site, run checks, return an LLM-ready shareable report.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with web accessibility analysis tools via MCP, enabling checks for alt text, heading hierarchy, color contrast, ARIA validation, and form accessibility.46 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to perform comprehensive SEO audits on web pages, including meta tags, headings, links, images, performance, and more, via a CLI or MCP server.181MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to audit URLs or raw HTML for SEO, AEO, and GEO performance, generate llms.txt manifests, and check the tool version via MCP tools.1MIT
- AlicenseAqualityBmaintenanceEnables running comprehensive website audits from any MCP client, returning actionable plain-language reports covering SEO, accessibility, performance, security, and more.685 npmMIT