Skip to content
crawlwise.

crawlwise in Windsurf

Windsurf reads MCP servers from ~/.codeium/windsurf/mcp_config.json. The file is shared by every workspace.

Point it at the server

{
  "mcpServers": {
    "crawlwise": {
      "serverUrl": "https://crawlwise.site/mcp"
    }
  }
}

Restart Windsurf afterwards. The MCP panel in Cascade should list the crawlwise tools once the server connects, and authorising it opens a browser for OAuth the first time.

Windsurf names the field serverUrl; other clients call it url. That one difference is the most common reason a config that works elsewhere silently does nothing here.

Verify it worked

In Cascade: "use crawlwise to list the free tools and what each one cannot do"

That call needs no key and no credit, so it is the right first test — if it answers, the transport and the auth are both working and anything that fails afterwards is a key or a plan question.

What it will not do

No score, no percentage, no verdict on whether a page will rank. An unmeasured value comes back as not measured and should stay that way in whatever the agent writes for you. If an agent summarises a crawlwise report and turns that into a zero, the summary is wrong rather than the report.

MCP reference · What crawlwise cannot tell you · Claude Code · Cursor