mcp-page-monitor
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-page-monitorMonitor https://example.com for changes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-page-monitor
MCP server for monitoring web page changes. Uses Playwright to capture page content, SQLite for snapshot storage, and optional LLM integration for business impact analysis.
Available on npm and the MCPize marketplace.
Tools
monitor_page
Register a URL to watch for changes. Takes an initial snapshot immediately.
Parameter | Type | Required | Description |
| string | yes | URL to monitor |
| string | no | Human-readable label |
| string | no | CSS selector to monitor a specific element |
| number | no | Check frequency (1–10080). Default: 60 |
check_changes
Browse a monitored URL with Playwright, capture current content, and diff against the stored snapshot.
Parameter | Type | Required | Description |
| string | yes | URL to check (must be registered first) |
Returns { changed, diff, timestamp } — diff includes added/removed line counts, changed sections, and a unified diff string.
analyze_change
Analyze a page diff using an LLM to summarize what changed and assess business impact.
Parameter | Type | Required | Description |
| string | yes | URL whose changes to analyze |
| string | no | Provide diff text directly instead of computing from snapshots |
Returns { summary, impact, severity } — severity is low | medium | high | critical.
Falls back to deterministic analysis (pattern matching for pricing changes, errors, policy updates, etc.) when no LLM endpoint is configured.
list_monitored_pages
List all URLs currently being monitored.
remove_monitored_page
Stop monitoring a URL.
Parameter | Type | Required | Description |
| string | yes | URL to stop monitoring |
Related MCP server: mcp-page-monitor
Installation
npm install mcp-page-monitorOr run directly:
npx mcp-page-monitorRequirements
Node.js 22+
Chromium browser (Playwright uses it for page rendering)
Install Playwright browsers if needed:
npx playwright install chromiumConfiguration
Claude Desktop / Cursor / MCP Client
Add to your MCP client config:
{
"mcpServers": {
"page-monitor": {
"command": "npx",
"args": ["mcp-page-monitor"],
"env": {
"PLAYWRIGHT_CHROMIUM_PATH": "/usr/bin/chromium-browser"
}
}
}
}Environment Variables
Variable | Default | Description |
|
| SQLite database location |
|
| Path to Chromium executable |
| — | Fallback browser path |
|
| Page navigation timeout |
| — | LLM API endpoint for |
| — | Bearer token for LLM endpoint |
|
| Model to use for analysis |
|
| Source identifier sent to LLM |
How It Works
Register a page with
monitor_page— takes an initial snapshot via headless ChromiumCheck for changes with
check_changes— fetches current content and computes a line-level diff (LCS-based) against the last snapshotAnalyze changes with
analyze_change— sends the diff to an LLM for business impact assessment, or uses built-in heuristics (pricing detection, error detection, policy changes) when no LLM is available
All snapshots are stored in a local SQLite database with WAL mode enabled for concurrent access.
Development
git clone https://github.com/deialedin/mcp-page-monitor
cd mcp-page-monitor
npm install
npm run build # Compile TypeScript
npm test # Run 26 tests
npm run dev # Watch mode with tsxLicense
MIT
Available Tools
5 toolsanalyze_changeA
Send a page diff to an LLM and get a business impact analysis including severity, change type, key changes, and recommended actions.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL whose changes to analyze | |
| diff_text | No | Optional: provide diff text directly instead of computing from latest snapshots |
check_changesA
Browse a monitored URL with Playwright, capture current content, diff against the stored snapshot, and return any changes found.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to check for changes (must be previously registered) |
list_monitored_pagesA
List all URLs currently being monitored for changes.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
monitor_pageA
Register a URL to watch for changes. Takes an initial snapshot immediately. Optionally specify a CSS selector to monitor a specific element.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to monitor for changes | |
| label | No | Human-readable label for this page | |
| selector | No | CSS selector to monitor a specific element instead of the full page | |
| check_interval_minutes | No | How often to check for changes (1 min to 7 days). Default: 60 |
remove_monitored_pageA
Stop monitoring a URL and deactivate it from the watchlist.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to stop monitoring |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
5 tool updates
v1.0.0- First observed
analyze_change - First observed
check_changes - First observed
list_monitored_pages - First observed
monitor_page - First observed
remove_monitored_page
TDQS
Scored across 5 tools
Each tool has a distinct role in the monitoring lifecycle: registering, checking, analyzing, listing, and removing. There is no overlap or ambiguity between their purposes.
All tool names follow a consistent verb_noun pattern (monitor_page, check_changes, analyze_change, list_monitored_pages, remove_monitored_page). The naming is uniform and predictable.
With exactly 5 tools, the set is well-scoped for a page monitoring service. Each tool covers a necessary operation without unnecessary bloat.
The core lifecycle of adding, checking, listing, and removing monitored pages is fully covered, plus an analysis step. A minor gap is the lack of an update operation (e.g., changing the CSS selector), requiring remove and re-add, but this is not a significant workflow blocker.
Maintenance
Related MCP Connectors
Recurring webpage change, price, inventory and metadata monitoring for autonomous agents.
Let your AI watch web pages, alert you to changes, and show what any page said on any past date.
Monitor web pages for price, stock or text changes; low-noise alerts via MCP, API and webhooks.
Page change monitoring, sitemap discovery, prompt-injection screening, clean markdown. Free preview.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables tracking web page changes, detecting content modifications with structured diffs and snapshot history through MCP tools.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to monitor web pages for content changes and receive alerts when changes occur.-
- FlicenseNot gradedqualityCmaintenanceEnables monitoring of website changes through contracts, with automatic extraction, semantic diffing, and healing, triggering alerts and actions via email, Slack, or Telegram.-
- AlicenseBqualityBmaintenanceEnables evidence-bearing change monitoring for public text pages, providing normalized diffing, SHA-256 hashing, and signed webhook notifications.6MIT