BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

screaming-frog-mcp

Connector Security Usable
Works inClaude Code Claude Cowork Claude Chat
Usable Scanned — metadata only

Enables automated site-wide security and compliance audits without manual intervention, reducing gap detection cycles and integrating crawl validation direct…

Headless MCP server for Screaming Frog SEO Spider – run crawls, export and analyze crawl data via the CLI. Small locked-down tool surface for scheduled audits, CI, and unattended AI agents.

79 starsMIT (commercial OK)FreeNo code needed
Reviewed 2026/06 ·
Usable rating — This tool is functional but has notable gaps. Review the evaluation notes below before deploying.
Why it matters

Enables automated site-wide security and compliance audits without manual intervention, reducing gap detection cycles and integrating crawl validation directly into CI/CD pipelines for continuous risk monitoring.

Best for

DevOps and security teams automating scheduled site crawls and compliance checks in headless or unattended environments.

Works in
Claude Code Claude Cowork Claude Chat
Source

https://github.com/bzsasson/screaming-frog-mcp

By bzsasson

How to Get It

Option 1: Claude Desktop AppOpen the Customize panel in the sidebar → browse connectors → search and add. Works in Claude Code, Claude Cowork, and Claude Chat.
Option 2: Paste into Claude CodeCopy the command below and paste it into a Claude Code conversation. Claude will run it for you.
Command
uv tool install screaming-frog-mcp

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

First thing to try

Once it’s connected, paste this into Claude:

Crawl a website and identify all broken links before deployment
PrerequisitesScreaming Frog SEO Spider installed locally (tested v23-24, works v16+); a paid SF license for most features (free tier caps crawls at 500 URLs and lacks headless CLI/exports); Python 3.10+. On Linux/Windows set SF_CLI_PATH to the SF CLI binary.CostFree

Trust Signals Auto-scanned

Stars79Contributors1Last updated2026-06-12LicenseMIT (OK for commercial use)Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-08-12 · scanner vattempted-no-data

Data & Access

Data processingPrompts sent to Anthropic API. Enterprise/Team plans exclude training.

Community Pulse New

No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 66 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

Things to check

  • Screaming Frog's crawl database allows one process at a time — you must close the SF GUI before the server can read or export crawl data (it detects this and errors clearly). Avoid uvx in MCP client configs: cold-cache resolution can exceed the 60-second initialize timeout; use a persistent uv tool or pip install instead. Deliberately limited to nine read-and-export tools — no script runner or filesystem writes.
  • Single maintainer. Consider the risk if this person stops maintaining the project.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation Scores

Evaluation

Ease of Use
3/5
Versatility
3/5
Reliability
3/5
Security
3/5
Overall score3.00 / 5.00 UsableEvaluatedJun 2026
Scored from trust signals (evidence-eval-v1): 66 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation →