Integrations overview
Site Health exposes your scan data through several integration surfaces. Pick the one that matches the tool you already use — you do not need to set up more than one.
Quick decision table
| You have / use | Use this integration | Auth | Setup time |
|---|---|---|---|
| Claude Pro or Claude Max | Claude.ai custom connector | OAuth 2.1 | ~1 min |
| Claude Desktop (local app) | Claude Desktop config | API key | ~2 min |
| Claude Code (CLI) | Claude Code skill | OAuth or API key | ~2 min |
| Cursor or Windsurf | Cursor / Windsurf config | API key | ~2 min |
| GitHub Actions / CI | Budget-check API | API key | ~5 min |
| No Claude subscription | Prompt export | None | 0 min |
| Webflow site publishing | Webflow publish webhook | Webflow signature | ~1 min |
What each option gives you
Claude.ai connector (OAuth) — the path of least resistance for Claude Pro/Max users. Paste one URL, approve in your browser, done. No API key to manage. Works on web and desktop Claude.ai.
Claude Desktop / Cursor / Windsurf (API key) — local AI apps that speak MCP but do not yet support Dynamic Client Registration. You generate a Site Health API key and paste it into the app's config file.
Claude Code skill — a site-health-audit skill that ships pre-written instructions so Claude Code follows the correct audit workflow automatically (identify site → fetch minimum required data → suggest Webflow-specific fixes). Uses whichever MCP transport you configured.
GitHub Actions / CI — a plain HTTP endpoint (/api/external/budget-check) that returns pass: true / pass: false plus the list of violated budgets. Fail your CI job when performance regresses.
Webflow publish webhook — Webflow pings Site Health every time you publish, and Site Health enqueues a fresh scan. Deduplicated so back-to-back publishes trigger at most one in-flight scan per site. Registered automatically during the Webflow OAuth connect, or you can add it manually in Webflow's Site Settings.
Prompt export — the escape hatch. If you don't want to configure any MCP client, use the "Copy as AI prompt" button on any site and paste the generated prompt into ChatGPT, Gemini, or Claude.ai free tier.
Base URL
All integrations use the same base URL:
https://sitehealth.octagramlabs.com
The MCP endpoint is /api/mcp. The CI endpoint is /api/external/budget-check. The webhook endpoint is /api/webhooks/webflow.
What's read-only vs. what writes
Everything here is read-only in v0.1. MCP tools query scan data. The budget-check API returns scores. The webhook only enqueues scans. Nothing mutates your Webflow project. Write operations (auto-fix, republish-on-regression) are gated behind explicit consent in a future release.
Where to go next
If you have any Claude subscription, start with the Claude.ai connector. If you are a Claude Code user, add the skill on top. If you run CI, wire up GitHub Actions regardless of which AI client you use.