Integrations
Use SiteInspect from the dashboard, in CI pipelines, or via MCP. We notify you where you already work.
We integrate with the tools you use
Scans from CI; alerts to your chat and ticketing. No new dashboard to check.
Dashboard
Web UI for scans, reports, and settings.
Sign in, create organizations, run multi-page scans, and view reports with score, findings, and PDF export. Usage and billing are per organization; metrics and readiness-over-time are filterable by org.
PricingCI / Pipeline
Run scans on deploy or on schedule.
Use the SiteInspect CI image or API to trigger scans from GitHub Actions, GitLab CI, or any pipeline. Pass your API key and target URL; get status and report link. Ideal for “accessibility checks in codebase” and pre-release checks.
CI docsMCP (Model Context Protocol)
Let AI assistants run scans for you.
The SiteInspect MCP server exposes tools so AI agents (e.g. in Cursor or other MCP clients) can start scans and fetch results. Same scans and limits as dashboard and CI; usage counts toward your org’s plan.
MCP setupAPI
REST API for scans and reports.
POST to create a scan, GET to poll status and fetch report. Use from CMS, design systems, or custom tooling. Optional webhook (when configured) can notify you when a scan completes.
DocsAlerts on high-severity findings
PagerDuty, Slack, JIRA, ClickUp
When a scan completes with critical or high-severity findings (severity 1 or 2), SiteInspect can send alerts to PagerDuty (trigger incident), Slack (webhook message), JIRA (create issue), or ClickUp (create task). Configure via environment variables; each destination is optional. See the repo docs/ALERTING.md for env vars and setup.