crawlwise in Claude Code

Add the server

claude mcp add --transport http crawlwise https://crawlwise.site/mcp

Then run /mcp inside Claude Code and authenticate when it prompts. The browser opens, you approve the scopes, and the tools appear for that session and every later one.

A person who would rather not use OAuth can paste an API key instead — create one (Pro plan or above) and pass it as a bearer token in the same command with--header.

Verify it worked

Ask Claude: "use crawlwise to check whether GPTBot can crawl example.com"

A working connection answers with a per-crawler verdict: allowed, blocked, challenged, or not established — and it will say “not established” rather than guessing when a fetch failed. If the list is empty, /mcp shows whether the server connected and what it reported.

What it costs

The free tool endpoints — AI crawler access, schema validation, Core Web Vitals and the rest of the toolkit — need no key and spend no credit. A full audit starts at 1.25 credits and the estimate is in the response before the work runs.

What it will not do

It will not invent a score, a percentage, or a readiness rating, because the service does not produce any. It cannot tell you whether Google will rank a page, and it will not present a checklist score as a Google score. When a value did not come back it says not measured — and a model reading that answer should not round it to zero.

MCP reference · What crawlwise cannot tell you · Cursor · Windsurf