Website audits and SEO fixes inside Cursor
Run squirrelscan from Cursor's terminal, or wire up the hosted MCP server for cloud audits.

Cursor is comfortable running shell commands, which means it's comfortable running squirrelscan. Drop in the CLI, ask the agent to audit a URL, and it reads the report the same way it reads a stack trace: as something to go fix.
You get two levels of integration. The CLI (plus the audit-website skill, which Cursor loads natively as an Agent Skill) covers quick local audits with zero setup. The hosted MCP server goes further: cloud audits with real browser rendering, a per-website issue tracker, and the audit engine wired in as native tools, running the full 260+ rule catalog with no shell piping required.
Neither path needs you to leave the editor. Cursor's agent can run the audit, read the results, and open the fixes across your codebase in one pass.
Setup
Run it locally
free · squirrel CLI on your machine- 1
Install the squirrelscan CLI
Run it in Cursor's built-in terminal. Local audits are free and need no account.
bashcurl -fsSL https://install.squirrelscan.com | bash - 2
Ask the agent to audit a URL
The llm format is compact and structured, so the agent can parse it straight out of the terminal without you summarizing anything.
bashsquirrel audit https://example.com --format llm - 3
Or install the squirrelscan skills
Installs all the squirrelscan skills. Cursor supports the Agent Skills standard natively and also loads skills from Claude Code's folders, so this adds an /audit-website command you invoke by typing / in the agent chat.
Skills install guidebashnpx skills add squirrelscan/squirrelscan
Run it hosted
cloud · rendering, scheduling, issue tracker, shareable reports- 1
For cloud audits, add the hosted MCP server
Create .cursor/mcp.json in your project (or ~/.cursor/mcp.json to make it available everywhere), then open Cursor Settings, find squirrelscan under Tools & Integrations, and click Needs login to authorize.
MCP client setup for Cursorjson{ "mcpServers": { "squirrelscan": { "url": "https://mcp.squirrelscan.com/mcp" } } }
Frequently asked questions
- Is squirrelscan free to use in Cursor?
- Local CLI and skill audits are free with no account. The hosted MCP server runs cloud audits on pay-as-you-go credits, and every account gets 500 free per month with no card required.How credits work
- How do I get Cursor to audit and fix my site's SEO?
- Install the audit-website skill and type /audit-website in the agent chat, or just ask the agent to audit a URL. Cursor runs the audit, reads the report, and edits the relevant files to fix what it finds, the same way it works from a failing test or a bug report.Fix your site with an agent
- Can I audit localhost or a staging site from Cursor?
- Yes for the CLI and skill: they audit anything Cursor's machine can reach, including localhost. The hosted MCP server crawls from squirrelscan's cloud and needs a publicly reachable URL, so use the CLI or the local squirrel mcp server for private networks.
- Do I need a squirrelscan account?
- No account for local CLI or skill audits. The hosted MCP server needs one: sign in with OAuth from Cursor's Tools & Integrations settings, or set an API key as a bearer header for CI and shared configs.
- Can Cursor audit my site on every deploy or in CI?
- Yes. Run squirrel audit in your pipeline with --fail-on to break the build when results regress; deterministic audits need no account, and cloud features read a SQUIRRELSCAN_API_KEY secret. There's an official GitHub Action too. Recurring scheduled audits run from the dashboard on the Pro plan.CI gating guide
Get started
Follow the docs quickstart, or see what a finished audit looks like.