Put website changes where your team already works.

PageCrawl watches the pages that matter and hands the result to the tool you actually use, whether that is an AI assistant, a chat channel, a spreadsheet or your own code. Everything here is included on every plan.

Start monitoring free

AI assistants and agents

One connection gives an assistant your monitors: it can create them, read what changed, and act on the result in conversation. The same MCP server works in every client below.

Claude

Claude web, desktop and Claude Code, over OAuth. No token to paste.

Set up →

ChatGPT

Connect PageCrawl as a connector and ask it what changed.

Set up →

Notion

Add PageCrawl to a Notion custom agent, then have it log changes into your own databases.

Set up →

Cursor, Cline, Windsurf, VS Code

Editor and CLI clients, over OAuth or a bearer token.

Set up →

Any MCP client

The server speaks the public Model Context Protocol, so any compliant client works.

Set up →

Automation and workflows

Send a detected change into whatever runs the rest of your process. Useful when the same thing should happen every time, without an assistant deciding.

Zapier

Trigger a Zap on every detected change.

Set up →

Make

Native app with OAuth, no webhook plumbing to maintain.

Set up →

n8n

Self-hosted or cloud, driven by webhooks or the MCP client tool.

Set up →

Home Assistant

Bring monitors into your dashboard as sensors.

Set up →

Webhooks

Signed POSTs to your own endpoint, with a payload you choose field by field.

Set up →

Alerts and reports

Where a change shows up when it is worth telling someone about.

Email

Per-change alerts and scheduled digests.

Set up →

Slack

Post changes into a channel, with the diff attached.

Set up →

Microsoft Teams

Adaptive cards into a Teams channel.

Set up →

Discord

Rich embeds into a Discord channel.

Set up →

Telegram

Direct messages or group posts, screenshots included.

Set up →

Web push

Browser notifications without an inbox.

Set up →

Scheduled reports

A digest on your schedule instead of an alert per change.

Set up →

Storage, export and archives

Keep the history somewhere you already work, or somewhere you can cite later.

Google Sheets

Every detected change appended as a row, with the columns you pick.

Set up →

Notion

Every detected change written into a Notion database as a new row.

Set up →

Dropbox

Screenshots and captured history synced to your own folder.

Set up →

Internet Archive

Preserve captured changes publicly in the Wayback Machine.

Set up →

Web evidence archives

Signed, timestamped WACZ archives for changes that may need proving.

Set up →

CSV and Excel export

Download history for a monitor, a folder or a whole workspace.

Set up →

Build your own

When none of the above is the shape you want.

REST API

Create monitors, read history and pull diffs from your own code.

Set up →

Push data sources

Send values in instead of crawling, and get the same history, charts and alerts.

Set up →

RSS feeds

Subscribe to detected changes in any reader.

Set up →

Embeddable widget

Put a live change feed on your own page.

Set up →

Browser extension

Start monitoring the page you are looking at.

Set up →

Common questions

Do integrations cost extra?

No. Every integration on this page is part of the product rather than a paid add-on, and the MCP server and REST API work on every plan, including Free. Your plan sets how many pages you monitor and how often they are checked, not which tools you may connect them to.

What is the difference between the MCP server and a webhook?

A webhook fires the same way every time: a change is detected, PageCrawl posts it to your endpoint, your code decides what happens. The MCP server is for an assistant working with you, so it can create monitors, read history and summarise what changed in the moment you ask. Use webhooks for repeatable pipelines and MCP for conversation.

Can I connect a tool that is not listed here?

Usually yes. Anything that accepts an incoming webhook can receive changes directly, and any client that speaks the Model Context Protocol can connect to the MCP server, including self-hosted ones. The list above is what we document, not what is technically possible.

How quickly does a change reach the tool I connect?

A change is delivered once a check detects it, so the check frequency you set on the monitor is what decides the delay. Alerts, webhooks and MCP results all read from the same detected change, so no integration is ahead of or behind the others.