mcp-page-monitor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROME_PATH | No | Fallback browser path | |
| LLM_API_KEY | No | Bearer token for LLM endpoint | |
| LLM_ENDPOINT | No | LLM API endpoint for analyze_change (e.g. OpenAI-compatible /v1/chat/completions) | |
| LLM_MODEL_ID | No | Model to use for analysis | gpt-4o-mini |
| PAGE_TIMEOUT_MS | No | Page navigation timeout | 30000 |
| LLM_SOURCE_SYSTEM | No | Source identifier sent to LLM | mcp-page-monitor |
| PAGE_MONITOR_DB_PATH | No | SQLite database location | ~/.mcp-page-monitor/page-monitor.db |
| PLAYWRIGHT_CHROMIUM_PATH | No | Path to Chromium executable | /usr/bin/chromium-browser |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| monitor_pageA | Register a URL to watch for changes. Takes an initial snapshot immediately. Optionally specify a CSS selector to monitor a specific element. |
| check_changesA | Browse a monitored URL with Playwright, capture current content, diff against the stored snapshot, and return any changes found. |
| analyze_changeA | Send a page diff to an LLM and get a business impact analysis including severity, change type, key changes, and recommended actions. |
| list_monitored_pagesA | List all URLs currently being monitored for changes. |
| remove_monitored_pageA | Stop monitoring a URL and deactivate it from the watchlist. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.