Let Claude Code audit and fix your website

1. 1

   Install the squirrelscan CLI

   One line, no account needed. Signed out, local audits are free and run entirely on your machine.

   bash

   curl -fsSL https://install.squirrelscan.com | bash

2. 2

   Run an audit in agent-friendly format

   Point it at a URL and ask Claude Code to read the result. The llm format is compact and structured, built for exactly this.

   bash

   squirrel audit https://example.com --format llm

3. 3

   Or install the squirrelscan skills

   Installs all the squirrelscan skills and gives Claude Code a /audit-website slash command, so it can run audits on its own without you typing the CLI invocation each time. It works in plan mode too, so Claude Code can draft a fix plan before touching any code. squirrel setup offers this on the first run, and auto-update keeps the skills current. Claude Code users can also grab everything, skills plus the hosted MCP server, as a plugin.

   bash

   squirrel skills install

   squirrel skills reference

1. 1

   For cloud audits, connect the hosted MCP server

   This is the deeper integration: cloud audits with browser rendering, the per-website issue tracker, and the rule catalog, all as native tools. Add the server, then run /mcp inside a session, select squirrelscan, and choose Authenticate to sign in and pick your organization.

   bash

   claude mcp add --transport http squirrelscan https://mcp.squirrelscan.com/mcp

   MCP client setup for Claude Code

Frequently asked questions

Is squirrelscan free to use with Claude Code?

Local audits are, when they run signed out or with --offline: the squirrel CLI and the audit-website skill run entirely on your machine with no account. Signed in, every audit uses pay-as-you-go credits (50 per audit plus 2 per audited page), a local run or a hosted MCP server audit alike, and every account gets 500 free every month, so most day-to-day use never touches a card.How credits work

How do I get Claude Code to actually fix my site's issues, not just list them?

Point Claude Code at the audit output, or run the audit-website skill in plan mode. It groups findings by category, maps them to files in your repo, and applies the fixes across your codebase. Re-audit afterwards and the issues it resolved stop showing up.

Can Claude Code audit my localhost or a staging site?

Yes. The local CLI and the audit-website skill audit any URL Claude Code's machine can reach, including localhost and internal staging. The hosted MCP server crawls from squirrelscan's cloud, so it needs a publicly reachable URL; for private networks, use the CLI or the local squirrel mcp server.

Should I use the skill or the hosted MCP server?

The skill wraps the local CLI, best for quick one-off audits from your machine. The hosted MCP server is the fuller integration: cloud audits with browser rendering, a shared per-website issue tracker, and the rule catalog as native tools. Reach for it once you want state that persists across sessions and teammates. Many people install both.Hosted MCP server

Can I run the audit on every deploy or on a schedule?

Yes. For CI, drop the squirrel CLI into your pipeline: it exits non-zero when scores regress, so the build fails like any other check. For hands-off recurring runs, scheduled cloud audits re-run from the dashboard on every plan: free schedules one site weekly, Pro goes daily on every site. And Claude Code can always just re-run an audit whenever you ask after a deploy.CI gating guide