Connect Sitepager to Your AI Assistant with MCP

Sitepager MCP connects your AI assistant directly to Sitepager.

It does not modify your website directly. It works alongside your existing tools as part of the scan → fix → verify workflow.

---

What you can do

Once connected, your assistant can:

• Create scans, run them, and wait for results
• Summarize issues across your entire site
• Identify broken pages and broken links
• Detect pages added or removed since the baseline
• Review visual changes against the baseline
• Investigate SEO issues on specific pages
• Retrieve Lighthouse reports from a scan and review performance issues

---

Requirements

• A Sitepager account
• An AI assistant that supports MCP (Claude Desktop or Claude Code recommended)

---

Get your API key

1. Log in to Sitepager
2. Go to Settings > API Keys
3. Create a new key and copy it

Create an API key in Settings > API Keys.

Your key starts with sp_live_. Keep it secure. It gives access to all scans and results in your workspace.

---

Connect Sitepager MCP

Most users should connect through the hosted endpoint. It requires no install and works with Claude Desktop, Claude Code, Cursor, Windsurf, and other MCP-compatible tools.

Choose your assistant below and follow the steps.

Claude Desktop

Claude Desktop connects through its built-in Connectors settings.

1. Go to Settings > Connectors
2. Click Add custom connector
3. Fill in the dialog:
   • Name: Sitepager
   • Remote MCP server URL: https://api-open.sitepager.io/v1/mcp?key=YOUR_API_KEY
4. Click Add

Add Sitepager in Settings > Connectors > Add custom connector.

Replace YOUR_API_KEY with the key you copied from the previous step.

Treat this URL as sensitive because it includes your API key. If you rotate your key, update the URL here.

Claude Code

Claude Code connects to Sitepager using an Authorization header, so your API key is not included in the URL.

Recommended: Add Sitepager globally

Run this once from any terminal:

claude mcp add --transport http --scope user sitepager \
  https://api-open.sitepager.io/v1/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Replace YOUR_API_KEY with the key you copied from the previous step.

This makes Sitepager available in every Claude Code session, regardless of which project you are in.

Advanced: Add Sitepager to one project only

If you want Sitepager available only in a specific project, add a .mcp.json file to that project’s root:

{
  "mcpServers": {
    "sitepager": {
      "type": "http",
      "url": "https://api-open.sitepager.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with the key you copied from the previous step.

Project-scoped setup is useful when you want separate keys for different workspaces, or when you want to share the setup with teammates.

If you commit .mcp.json, use an environment variable instead of an inline key:

"Authorization": "Bearer ${env:SITEPAGER_KEY}"

Cursor / Windsurf

Cursor and Windsurf both connect to Sitepager with a config file.

Use the config for your editor below.

Cursor

Add this to .cursor/mcp.json in your project root, or to ~/.cursor/mcp.json to make Sitepager available in all projects:

{
  "mcpServers": {
    "sitepager": {
      "url": "https://api-open.sitepager.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Windsurf

Add this to ~/.codeium/windsurf/mcp_config.json on macOS/Linux, or %USERPROFILE%\.codeium\windsurf\mcp_config.json on Windows.

Create the file if it does not exist.

{
  "mcpServers": {
    "sitepager": {
      "serverUrl": "https://api-open.sitepager.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with the key you copied from the previous step.

Note: Windsurf uses serverUrl; Cursor uses url.

To avoid storing your key in the file, use an environment variable:

"Authorization": "Bearer ${env:SITEPAGER_KEY}"

Other

If your assistant supports remote MCP servers, use:

• Server URL: https://api-open.sitepager.io/v1/mcp
• Authorization header: Bearer YOUR_API_KEY

Replace YOUR_API_KEY with the key you copied from the previous step.

If your assistant does not support remote MCP servers, see the Advanced: Local install tab.

Advanced: Local install

Use this only if your assistant does not support remote MCP servers, or if you prefer running the @sitepager/mcp-server package on your machine.

Add the following MCP server config to your assistant:

{
  "mcpServers": {
    "sitepager": {
      "command": "npx",
      "args": ["-y", "@sitepager/mcp-server"],
      "env": {
        "SITEPAGER_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with the key you copied from the previous step.

---

Verify the connection

Start a new session and ask:

Prompt

List my Sitepager scans.

Your assistant should return a list of your scans. If it does, the MCP connection is working.

Once connected, you can run scans, review issues, and verify changes directly from your assistant.

---

Example prompts

Run a Sitepager scan for https://example.com and summarize the results.

Run the [scan name] scan and wait for it to complete.

Summarize the most important issues in the latest run of [scan name].

Are there any broken pages or broken links in the latest run of [scan name]?

Which pages have visual differences from the baseline in [scan name]?

What SEO issues exist on /pricing in the latest run of [scan name]?

Review the Lighthouse results for the landing page from the latest run of [scan name]. Summarize the scores and flag anything that needs attention.

---

What to do next

• Scan, Fix, Verify with AI — learn the universal fix workflow
• Fix Webflow Issues with AI — apply the workflow to a Webflow site