AI coding assistants like Claude and Cursor are changing how developers interact with tools. Instead of switching between dashboards, terminals, and browser tabs, you describe what you need and the agent handles the rest. Website monitoring is a natural fit for this workflow. You should be able to ask "what changed on my competitor's pricing page this week?" and get an answer without opening a separate app.
PageCrawl is the only dedicated web monitoring tool with a purpose-built MCP (Model Context Protocol) server. This means Claude Code, Cursor, Windsurf, and any MCP-compatible AI tool can create monitors, check for changes, review diffs, and manage your monitoring setup through conversation.
This guide covers what the MCP server can do, practical examples, and how to set it up.
What Is MCP and Why Does It Matter for Monitoring
The Model Context Protocol is an open standard that lets AI assistants connect to external tools and data sources. Instead of the AI guessing about your monitoring data or asking you to copy-paste results, MCP gives it direct access to your actual monitors, change history, and configurations.
For web monitoring, this means:
- No context switching. Ask about changes without leaving your editor or terminal.
- Natural language queries. "Show me all price changes across my competitor monitors this month" works as a query.
- Automated workflows. AI agents can set up monitors, trigger checks, and process results as part of larger tasks.
- Living knowledge base. Your monitored pages become queryable data, not just an alert feed.
What You Can Do with the PageCrawl MCP Server
The MCP server exposes 14 tools that cover the full monitoring lifecycle:
Viewing and Searching
- List all monitors across all your workspaces, with optional search by URL, domain, or name
- Get monitor details including configuration, last check status, and tracking mode
- View monitoring history for any monitor, with date filtering
- Get the latest values from tracked elements (current price, availability status, page content)
- View formatted diffs showing exactly what changed in a specific check
Creating and Managing
- Add new monitors with simplified tracking modes (price, reader, fullpage, content_only, specific_text, specific_number)
- Trigger immediate checks on any monitor without waiting for the schedule
- Manage tags on monitors for organization
- Mark changes as seen on one or all monitors
- List and configure workspaces
- Set workspace defaults for screenshots, notifications, frequency, and AI focus
Practical Examples
Here are real prompts you can use with Claude Code or Cursor once the MCP server is connected:
Setting Up Monitors
"Add a price monitor for https://store.example.com/product-123
with availability tracking"The AI creates the monitor with the right tracking mode, elements, and default settings. No need to configure selectors or choose between tracking types.
"Monitor these 5 competitor pricing pages and tag them all as 'q2-pricing'"Batch creation with tagging in a single conversation turn.
Checking for Changes
"What changed across all my monitors in the last 7 days?"Returns a summary of recent changes with priorities, timestamps, and affected monitors.
"Show me the diff for the last change on the Acme Corp pricing page"Returns a formatted text diff showing exactly what was added, removed, or modified.
Research and Analysis
"What is the current price on each of my competitor product monitors?"Pulls the latest tracked values across all price monitors, giving you a competitive pricing snapshot without visiting any dashboards.
"Have any of my compliance monitors changed in the last 30 days?
Show me the details."Filters by tag or search term, then retrieves change history and diffs for matching monitors.
Workflow Integration
"Set up a monitor for our competitor's changelog at
https://competitor.com/changelog using reader mode,
check every 15 minutes, and tag it as 'competitor-intel'"Creates a fully configured monitor with frequency, tracking mode, and tags in one step. The next time the competitor pushes an update, you will get notified through your configured channels.
How It Compares to Other Approaches
Several scraping tools offer MCP servers (Firecrawl, Apify, Bright Data), but these are built for one-time data extraction, not ongoing monitoring. They can fetch a page right now, but they cannot:
- Track changes over time. No history, no diffs, no "what changed since last week."
- Send notifications. No email, Slack, Discord, or Teams alerts when something changes.
- Score change importance. No AI priority scoring to filter noise from signal.
- Handle protected sites. No managed proxy infrastructure or bot protection handling.
A scraping MCP server answers "what does this page say right now?" PageCrawl's MCP server answers "what has changed, when, and does it matter?"
No other dedicated monitoring tool (Visualping, Distill.io, Hexowatch, ChangeTower, ChangeDetection.io) offers MCP integration. If you want AI agents to interact with your web monitoring data, PageCrawl is currently the only option.
Setting Up the MCP Server
The PageCrawl MCP server is available on all plans, including Free. Paid plans unlock write access (creating monitors, triggering checks).
Step 1: Sign up or log in at pagecrawl.io.
Step 2: The MCP server is pre-configured and hosted. Connect it from your AI tool's MCP settings using the PageCrawl provider. No API keys or local installation needed.
Step 3: Start using it. Ask your AI assistant to "list my PageCrawl monitors" to verify the connection is working.
For Claude Code Users
Add PageCrawl as an MCP server in Claude Code settings. Once connected, all 14 monitoring tools are available in your conversations. You can create monitors, check changes, and manage your setup without leaving the terminal.
For Cursor Users
Connect the PageCrawl MCP server through Cursor's MCP configuration. The monitoring tools integrate naturally into your coding workflow, so you can check for API changes or competitor updates while working on code.
Tips for Getting the Most Out of It
Start with what you already monitor. If you have existing monitors, use the MCP server to query them: "summarize all changes from last week" or "which monitors have unseen changes?" This is the fastest way to see the value.
Use tags for organization. Tag monitors by project, client, or category. Then query by tag: "show changes on all monitors tagged 'client-acme'."
Combine with AI importance filtering. Set a "What matters" prompt on your monitors (e.g., "Focus on price changes, ignore navigation updates"). The AI will score changes accordingly, and when you query via MCP, the priority scores help you focus on what matters.
Trigger checks on demand. Before a meeting or review, trigger checks on key monitors: "trigger a check on all my competitor pricing monitors." Results are available within minutes.
Choosing your PageCrawl plan
PageCrawl's Free plan lets you monitor 6 pages with 220 checks per month, which is enough to validate the approach on your most critical pages. Most teams graduate to a paid plan once they see the value.
| Plan | Price | Pages | Checks / month | Frequency |
|---|---|---|---|---|
| Free | $0 | 6 | 220 | every 60 min |
| Standard | $8/mo or $80/yr | 100 | 15,000 | every 15 min |
| Enterprise | $30/mo or $300/yr | 500 | 100,000 | every 5 min |
| Ultimate | $99/mo or $990/yr | 1,000 | 100,000 | every 2 min |
Annual billing saves two months across every paid tier. Enterprise and Ultimate scale up to 100x if you need thousands of pages or multi-team access.
At an engineering hourly rate, Standard at $80/year pays for itself the first time you catch a breaking API change, a deprecated endpoint, or a silent config change before it takes down production. 100 monitored pages is enough to cover the changelogs and docs of every third-party API your stack depends on. Enterprise at $300/year adds higher check frequency, 500 pages, and full API access. All plans include the PageCrawl MCP Server, which plugs directly into Claude, Cursor, and other MCP-compatible tools. Developers can ask "what changed in the Stripe API docs this month?" and get a summary pulled from your own monitoring history. Paid plans unlock write access so AI tools can create monitors and trigger checks through conversation, turning your tracked pages into a living knowledge base instead of a pile of alert emails.
Getting Started
Start with 3-5 pages you already check manually: a competitor's pricing page, an API changelog, a regulatory page, or a product you are waiting to restock. Set them up through the MCP server in a single conversation. Run it for two weeks and see how many manual checks it replaces.
Once you see the value, expand to cover your full competitive landscape, compliance requirements, or technical dependencies. The MCP server makes scaling from 5 monitors to 100 as simple as describing what you want to track.
PageCrawl's free tier includes 6 monitors and MCP access. Create your account and connect the MCP server to start monitoring from your AI assistant.