Crawlwise

What Crawlwise MCP server does

Crawlwise MCP server gives an AI agent access to Crawlwise page audits. The audit covers SEO issues and checks related to AI crawlers. Its workflow is designed around reviewing a page, addressing items marked as priority, and auditing the page again to identify remaining findings.

Each reported finding is tied to the check that generated it. The system also distinguishes between measured results and unavailable measurements. It does not fill gaps with estimated scores, so an agent can tell which conclusions are supported by an actual check.

The repository contains the agent-facing parts of Crawlwise rather than the audit engine itself. The engine runs at crawlwise.site. The project includes a Claude Code plugin, an MCP configuration, the Crawlwise skill, and workflows for audit-and-fix, AI search, and pre-launch tasks.

How it works

Crawlwise MCP server is exposed at https://crawlwise.site/mcp. In Claude Code, the plugin bundles the skill and MCP configuration. On first use, the MCP server signs the user in through OAuth. The README states that MCP access is available on the Pro plan and above.

An agent can request an audit for a URL and use the returned findings to guide changes. The documented operating pattern is to fix priority items and re-audit until no applicable findings remain. The material does not define a separate list of MCP tool names, so integrations should be evaluated by the audit workflow and the resulting report rather than by assumed tool names.

For agents using only the skill, installation copies the skill into the Claude and agents skill directories. Without an account, the skill uses the free CLI and its one-page-per-day limit. Supplying CRAWLWISE_API_KEY, or using the MCP server, provides the full report according to the README.

Setup and configuration

Claude Code users can add the marketplace and install the plugin with:

/plugin marketplace add Adnanarodiya/crawlwise-skills
/plugin install crawlwise@crawlwise

The MCP endpoint handles OAuth during first use, so the provided material does not specify a required server environment variable. The repository also documents a skill-only installation:

npx crawlwise skills install

That command places the skill in ~/.claude/skills/crawlwise and ~/.agents/skills/crawlwise. Alternatively, copy plugins/crawlwise/skills/crawlwise into an agent's skills directory. The CLI and API-key paths are alternatives to MCP, not additional MCP server configuration described in the repository.

Crawlwise MCP server fits teams that want an agent to inspect a page before launch, check AI search-related considerations, or perform an audit-and-fix loop. It is less suitable if the required plan, OAuth flow, or hosted audit dependency is unavailable.