# PageGuard MCP [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/pageguard/pageguard-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 120  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/pageguard-mcp

## Description
Privacy compliance scanning for AI coding tools. Detects tracking tech, cookies, and data gaps.

## Tools
Capabilities this server exposes over MCP:

- **pageguard_scan_local** — Scan a local project directory for privacy-relevant technologies by checking package.json dependencies, config files, and .env files against known tracking/analytics signatures. No API key or network access needed. Returns a ComplianceReport with detected technologies, data types collected, cookies, and third-party processors.
- **pageguard_scan_url** — Scan a live website URL for privacy compliance issues. Detects tracking technologies, cookies, third-party data collection, and compliance gaps by analyzing the actual deployed site. Returns a ComplianceReport with risk score, detected technologies, and compliance gaps. Optionally uses PAGEGUARD_API_KEY env var for authenticated requests.
- **pageguard_generate_docs** — Generate AI-written legal compliance documents (privacy policy, terms of service, cookie policy, etc.) for a previously scanned site. Requires a scanId from a prior URL scan and a PAGEGUARD_API_KEY with available credits. Document types: 'single' ($29 — privacy + terms + cookie), 'bundle' ($49 — everything), 'addon_security' ($19), 'addon_a11y' ($19), 'addon_schema' ($19), 'app_bundle' ($39), 'submission_guide' ($19).

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "pageguard-mcp": {
    "command": "npx",
    "args": ["pageguard-mcp"],
    "env": {
      "PAGEGUARD_API_KEY": "",
      "PAGEGUARD_API_URL": ""
    }
  }
}
```

**Requires environment variables:** `PAGEGUARD_API_KEY`, `PAGEGUARD_API_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What PageGuard MCP MCP server does

PageGuard MCP MCP server exposes PageGuard’s privacy compliance checks to MCP-compatible AI coding assistants. It covers two scanning paths: a local project inspection and a live website assessment. The local tool looks for privacy-relevant signals in a project’s `package.json`, configuration files, and `.env` files. Its report can include detected technologies, data types, cookies, and third-party processors.

The URL tool examines a deployed website and returns a compliance report with a risk score, detected technologies, and identified compliance gaps. A third tool generates AI-written legal compliance documents based on a scan. Supported document choices include privacy policies, terms of service, cookie policies, security guides, accessibility reports, schema markup, and app submission guides, depending on the selected document type.

## How it works

The PageGuard MCP MCP server provides three tools over MCP:

- `pageguard_scan_local` accepts an optional project path. If no path is supplied, it uses the current working directory. The local scan does not require an API key and does not make network requests.
- `pageguard_scan_url` requires a complete website URL, such as `https://example.com`. It uses the PageGuard service to inspect the live site and returns a scan result containing a scan ID.
- `pageguard_generate_docs` requires the scan ID from an earlier URL scan. Its optional `documentType` selects the document package to generate and defaults to `bundle`.

URL scanning and document generation require a PageGuard API key. Scanning itself is free, while generated documents consume credits according to the selected package or add-on.

## Setup and configuration

Install the server through `npx` and register it in an MCP client configuration. Claude Code uses a project `.mcp.json` or a global MCP configuration. Cursor adds the same server definition under MCP Servers, and Windsurf accepts it in its MCP configuration.

A basic configuration starts the server with `npx` and the `pageguard-mcp` package. Set `PAGEGUARD_API_KEY` when using URL scans or document generation. It is optional for local scans. `PAGEGUARD_API_URL` can override the default API base URL, which is `https://www.getpageguard.com`.

## Tools and capabilities

The local scan is suited to reviewing an in-development project before deployment, especially when its privacy signals are represented in dependencies, configuration, or environment files. The URL scan is suited to checking the behavior and compliance posture of an accessible site. Document generation uses a completed URL scan rather than accepting a site URL directly.

Available document selections include `single`, `bundle`, `addon_security`, `addon_a11y`, `addon_schema`, `app_bundle`, and `submission_guide`.

## Limitations and notes

Local scanning and URL scanning produce reports; they do not automatically modify project files or website code. Document generation requires a scan ID from `pageguard_scan_url`, so it is not a standalone document-writing tool. Local scans work without credentials, but API-backed features require an account API key. The generated documents are described as AI-written legal compliance documents, so developers should determine whether additional legal review is appropriate for their use case.

_Full upstream README: https://allmcps.com/mcp/pageguard-mcp/readme_