# SEO for Windsurf via MCP

> Run SEO audits in Windsurf via MCP. Add the Crawlwise server to mcp_config.json, sign in with OAuth, verify it connected, and know what it will not do.

Canonical: https://crawlwise.site/docs/windsurf

Crawlwise gives Windsurf SEO audits and AI crawler checks through MCP. 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 check which AI crawlers can read https://example.com"
```

That call spends no credits, so it is the right first test. If it answers, the transport and the sign-in are both working, and anything that fails afterwards is a plan or credit question. MCP access itself needs Growth or Agency.

## 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](https://crawlwise.site/docs/mcp) · [What crawlwise cannot tell you](https://crawlwise.site/limits) · [Claude Code](https://crawlwise.site/docs/claude-code) · [Cursor](https://crawlwise.site/docs/cursor)