Crawlinx MCP Server

Free technical-SEO audit MCP: crawl a site, run checks, return an LLM-ready shareable report.

Remote serverstreamable-http

What is the Crawlinx MCP server?

Most AI and media services work still happens through a UI a human drives. Crawlinx MCP server moves it into the conversation instead. Free technical-SEO audit MCP: crawl a site, run checks, return an LLM-ready shareable report.

The short version

The server is remote — you only need the endpoint https://crawlinx.com/mcp. No key.

This repository documents the hosted Crawlinx MCP server. The audit engine is operated as a service at crawlinx.com; this repo is the public reference and install guide for the MCP integration.

The tools it exposes

The server publishes 5 tools. What each one is for:

  • scan_url — Start a free SEO audit of a URL (crawls max_pages pages — default 50, max 200); returns a scan id
  • get_report — Fetch a finished report as structured JSON
  • get_report_markdown — Fetch a finished report as compact, LLM-ready Markdown (health score + prioritized fix plan + issues collapsed by code). Set full=true for the
  • get_issue_detail — Expand one issue code: every affected URL plus step-by-step remediation
  • diff_scan — Diff a scan against the previous scan of the same domain to confirm fixes landed and nothing regressed

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Crawlinx's toolset — scan_url, get_report, get_report_markdown and 2 more — is a fair guide to whether it matches your workflow. It is maintained by im-ff; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
scan_urlStart a free SEO audit of a URL (crawls max_pages pages — default 50, max 200); returns a scan id.
get_reportFetch a finished report as structured JSON.
get_report_markdownFetch a finished report as compact, LLM-ready Markdown (health score + prioritized fix plan + issues collapsed by code). Set full=true for the complete report.
get_issue_detailExpand one issue code: every affected URL plus step-by-step remediation.
diff_scanDiff a scan against the previous scan of the same domain to confirm fixes landed and nothing regressed.

Example prompts to try

  • Use Crawlinx to scan url.
  • Use Crawlinx to get report.
  • Use Crawlinx to get report markdown.

Frequently asked questions

It connects Crawlinx to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (scan_url, get_report, get_report_markdown, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Crawlinx directly.