PageLens AI - MCP Server

Connect PageLens AI reports to Claude Desktop, Cursor, Codex, and other MCP clients so your AI assistant can understand what failed, why it matters, and what to fix next.

An MCP (Model Context Protocol) server that gives AI agents direct access to PageLens AI - the independent launch reviewer for AI-built websites. PageLens AI turns launch risk across UX, SEO, Performance, Accessibility, Security, Conversion, and QA journey audits into plain-English priorities and agent-ready fix context.

Plug it into Cursor, Claude Desktop, Codex, or any MCP-compatible client and your agent can read scan results, drill into findings, surface quick wins, record owner decisions, and help close the fix loop without leaving the IDE.

MCP Endpoint

https://www.pagelensai.com/api/mcp

This is a remote MCP server — no local install required.

Which PageLens Path Is This?

• Launch Pack is for founders, marketers, and AI builders who want a one-off repair loop: owner-first verdict, fix prompts for their AI builder, Markdown export, desktop + mobile review, and a re-scan.
• CLI/API/deploy hooks are for Pro+ users who want PageLens AI to create scans from CI, release scripts, and client workflows.
• MCP is for AI assistants that need to read a PageLens report, understand the owner launch verdict, inspect the evidence, and help you patch or triage findings.

If you do not want to read technical detail, start in the PageLens web report and copy the fix prompt into Lovable, Bolt, Replit, Cursor, Codex, Claude Code, Copilot, or Windsurf. If you do want your coding agent to work directly with the report data, connect this MCP server.

Quick Start

Cursor

Add to your ~/.cursor/mcp.json (or workspace .cursor/mcp.json):

{
  "mcpServers": {
    "pagelens": {
      "url": "https://www.pagelensai.com/api/mcp"
    }
  }
}

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "pagelens": {
      "type": "http",
      "url": "https://www.pagelensai.com/api/mcp"
    }
  }
}

Codex CLI

Add to ~/.codex/config.toml:

[mcp_servers.pagelens]
url = "https://www.pagelensai.com/api/mcp"

Generic / other clients

Use the streamable HTTP endpoint:

https://www.pagelensai.com/api/mcp

Authentication

This server uses OAuth 2.0. Your MCP client will open a browser window to authorize with your PageLens account on first connect. No API keys to manage.

Scopes granted on authorization:

Available Tools

whoami

Confirm which PageLens account this MCP session is operating on, plus granted OAuth scopes.

{}

list_domains

List the domains you've verified ownership of, along with badge tier and the scan currently anchored to the public badge.

{
  "include_unverified": false
}

list_scans

List your most recent PageLens scans. Filter by status, domain, or date. Returns a slim summary per scan (id, URL, score, grade, severity counts, and launchVerdict). Scans may include launchContext with builderPlatform and launchMoment so agents can frame fixes for the owner's workflow without changing evidence or severity. QA Audit scans include a compact qaAudit summary with confidence, journey-step count, pages reviewed versus page budget, blocked/needs-review step counts, auth-profile status, and the reason fewer than the page budget were captured when the safe same-origin link graph is exhausted.

{
  "limit": 20,
  "status": "COMPLETE",
  "domain": "example.com",
  "since": "2026-01-01T00:00:00Z"
}

Status values: PENDING · RUNNING · COMPLETE · `FAILE

... View full README on GitHub