Let Codex CLI audit and fix your website
Connect the squirrelscan MCP server in two commands. Codex runs the audit, reads 300+ checks across SEO, performance, security and accessibility, and ships the fixes.
Connect in two commands
codex mcp add squirrelscan --url https://mcp.squirrelscan.com/mcp
codex mcp login squirrelscan
# CI: put --bearer-token-env-var SQUIRRELSCAN_API_KEY on codex mcp add, skip the login
Codex CLI runs shell commands as part of its normal workflow, so pointing it at squirrelscan takes about as long as installing the CLI. Tell it to audit a URL and it drives the command itself, reads the output, and starts proposing fixes.
If you want Codex to reach for audits, reports, and the issue tracker as first-class tools instead of parsed terminal text, connect the hosted squirrelscan MCP server. It's two commands: one to add the server, one to sign in.
How do you check which MCP servers are enabled in Codex?
Run codex mcp list to print every configured server with its status. Codex reads them from ~/.codex/config.toml, so you can also open that file directly to see what is registered.
codex mcp list prints two tables: stdio servers with their command, args, and working directory, and streamable HTTP servers with their URL. Both carry a Status column reading enabled or disabled, and an Auth column, so a server you added but later turned off is visible rather than silently absent.
codex mcp get <name> narrows that to one server and prints its transport, URL, and bearer token environment variable. It is the faster check when you want to confirm how a specific server is wired rather than what is installed overall.
Adding a server writes to the same file, so codex mcp add and a hand-edit of ~/.codex/config.toml are interchangeable. Adding squirrelscan for a headless run looks like codex mcp add squirrelscan --url <url> --bearer-token-env-var SQUIRRELSCAN_API_KEY.
codex mcp list
codex mcp get squirrelscanSetup
Codex CLI setup docsRun it locally
squirrel CLI on your machine · free signed out- 1
Install the squirrelscan CLI
Local audits run wherever your Codex session has shell access, free when signed out or with --offline.
CLI install and quickstartbashcurl -fsSL https://install.squirrelscan.com | bash - 2
Ask Codex to audit a site
In a Codex CLI session, describe the task in plain language. It runs the CLI and summarizes the results.
textRun squirrel audit https://example.com --format llm and tell me the top 3 issues to fix first
Run it hosted
cloud · rendering, scheduling, issue tracker, shareable reports- 1
Connect the hosted MCP server
codex mcp add registers the streamable HTTP server, codex mcp login runs the browser OAuth sign-in. The token lands in Codex's own credential store, not in config.toml, so a committed config stays clean.
MCP client setup for Codex CLIbashcodex mcp add squirrelscan --url https://mcp.squirrelscan.com/mcp codex mcp login squirrelscan - 2
Or use an API key for headless runs
For CI or a machine without a browser, skip OAuth and point Codex at an environment variable holding a squirrelscan API key. Codex reads it at connect time and sends it as a bearer token.
bashcodex mcp add squirrelscan --url https://mcp.squirrelscan.com/mcp \ --bearer-token-env-var SQUIRRELSCAN_API_KEY
Frequently asked questions
- How do I get Codex to fix my site's SEO?
- Install the squirrel CLI, then in a Codex session ask it to run squirrel audit <url> --format llm and fix the top issues. Codex reads the compact report, maps each finding to the file it comes from, edits the code, and can re-run the audit to confirm the fix. For a guided loop, install the skills with squirrel skills install (or let squirrel setup do it) and prompt Codex to use the audit-website skill.Fix your site with an AI agent
- Do I need an account, or is it free?
- No account is needed for local CLI audits: signed out, or with --offline, they are free and run wherever Codex has shell access. Signing in unlocks the cloud, which adds browser rendering, scheduled audits, the issue tracker, and shareable reports, and from then on every audit spends credits (50 per audit plus 2 per audited page). Every account gets 500 free credits per month, and audits beyond that spend credits pay-as-you-go. run_audit returns a cost estimate for Codex to show you before anything runs.How credits work
- Can Codex use squirrelscan as native tools instead of parsing terminal output?
- Yes. Run codex mcp add squirrelscan --url https://mcp.squirrelscan.com/mcp then codex mcp login squirrelscan to connect the hosted server. Codex then calls tools like run_audit, get_report, and list_issues directly, so it can poll a running audit, work the issue tracker, and browse the rule catalog without shelling out each time. Piping squirrel report --format llm into a prompt still works with zero setup for one-off audits.Hosted MCP server
- Can I connect squirrelscan from CI or a headless container?
- Yes. Instead of the browser OAuth flow, add the server with --bearer-token-env-var SQUIRRELSCAN_API_KEY and export a squirrelscan API key. Codex reads the variable at connect time and sends it as an Authorization bearer token, so no browser is needed. Mint a key with squirrel keys create --shell.
- Can I limit squirrelscan to one project instead of every Codex session?
- codex mcp add and codex mcp login only write the global ~/.codex/config.toml. To scope it to a single project, hand-write the same [mcp_servers.squirrelscan] block into that project's .codex/config.toml, which Codex loads once the project is trusted.
Get started
Follow the docs quickstart, or see what a finished audit looks like.