All integrations

Monitor any web page from Claude

claude
vp
mcp

Visualping is listed in Claude's Connectors Directory. Ask Claude for a monitor in plain language, and Visualping keeps checking on schedule after the chat ends.

Setup

Connect in three steps

No server URL to paste and no API key to copy.

1

Open Visualping in Claude

In Claude, go to Customize, then Connectors, and find Visualping in the directory. The button below opens the listing.

2

Connect and sign in

Connect it, sign in with your Visualping account, then select Allow. Claude gets the permissions of your Visualping role and nothing more.

3

Ask for a monitor

Describe the page and the changes that matter. Claude creates the monitor and can confirm what the first capture picked up. Visualping then checks it on schedule from its own servers, whether or not Claude is open.

Watch https://example.com/pricing every day and tell me when a plan price changes.

On a Claude Team or Enterprise plan?

An organization Owner adds the connector first. After that, each member connects with their own Visualping account, so everyone keeps their own role and workspaces.

Using Claude Code or another AI client?

The same Visualping server works in Claude Code, ChatGPT, Codex, Grok, Cursor and VS Code.

What you can ask

Requests Claude can run in your Visualping account

Each request uses one or more of the connector's 18 tools.

“Watch this pricing page every day and alert me only when a plan price changes. Then show me what the first capture picked up.”

Creates a monitor with a plain-language alert condition, waits for the first check and reads back what the page showed.

  • create_monitor
  • wait_for_monitor_check

“What changed on my monitors this week? Start with the important ones.”

Reads the change timeline with important changes first, each with its Visualping AI summary and Important flag.

  • get_timeline

“Flag the two pricing changes in red and hide the cookie banner one.”

Flags changes in a colour everyone in your workspace sees, and hides noise from the timeline without deleting it.

  • flag_change
  • hide_change

“Post alerts from the pricing monitors to #pricing-watch in Slack and stop the emails.”

Changes where a monitor sends its alerts: email, SMS, Telegram, Slack channels, and webhooks for Microsoft Teams, Discord and n8n, within what your plan includes. Slack and Telegram must already be connected to your account.

  • set_monitor_notifications

“Dismiss the cookie banner and open the Pricing tab before each check.”

Sets the steps a monitor runs before every capture, for content that is not on the page as it first loads.

  • set_monitor_actions

“Only check during business hours, Monday to Friday, and pause the campaign monitors.”

Limits checks to a daily window in your account's time zone, and pauses monitors while keeping their history.

  • set_monitor_schedule
  • deactivate_monitor
Tools

All 18 tools, in five groups

These are the same tools Visualping's own assistant uses.

See your account and monitors

  • describe_userRead

    Your account type, plan, check balance, active monitor count and workspaces.

  • get_monitorsRead

    Lists your monitors, with filters for status and label.

  • get_monitor_settingsRead

    The full setup of one monitor: what it watches, how often, its alert condition, schedule, page actions and alert destinations.

Create a monitor and confirm it works

  • create_monitorWrite

    Starts watching a URL and runs the first check straight away, with an optional alert condition, page actions and alert destinations.

  • wait_for_monitor_checkRead

    Waits for a check to finish and returns the captured page text and screenshot, so Claude can confirm the monitor sees what you asked for.

  • run_monitorWrite

    Runs a check now instead of waiting for the next scheduled one.

Tune a monitor

  • update_monitorWrite

    Changes a monitor's URL, name, check interval or alert condition.

  • set_monitor_scheduleWrite

    Limits checks to a daily time window on the weekdays you choose.

  • set_monitor_actionsWrite

    Sets steps to run before each capture, such as dismissing a cookie banner or opening a tab.

  • set_monitor_notificationsWrite

    Chooses where alerts go: email, SMS, Telegram, Slack channels or webhooks.

Review what changed

  • get_timelineRead

    Detected changes across your monitors, filtered by monitor, date and importance.

  • flag_changeWrite

    Flags a change for follow-up, in a colour if you like.

  • unflag_changeWrite

    Removes a flag.

  • hide_changeWrite

    Hides a change from the timeline without deleting it.

  • unhide_changeWrite

    Brings a hidden change back.

Pause, resume or delete

  • deactivate_monitorWrite

    Pauses a monitor and keeps its history.

  • activate_monitorWrite

    Resumes a paused monitor.

  • delete_monitorWrite

    Deletes a monitor and its history for good.

How to read the labels

Read

Five tools only read. They never change a monitor.

Write

Thirteen tools change something. Claude may ask you to confirm before it runs one.

Plans and limits

The connector uses your plan's pages and checks

It comes with every Visualping plan, including Free, at no extra charge.

Pages

Every page Claude sets up counts as one of your plan's pages. At the limit, the monitors you have keep running. Pause one or add pages to start another.

Checks

A monitor uses one check each time it checks a page: its first check, its scheduled checks, a check you ask Claude to run now, and a fresh capture after a setup change. If you run out, monitoring pauses until your monthly allowance resets or you change plans.

Frequency

Your plan sets how often a page can be checked. The Free plan checks as often as hourly, and paid plans allow shorter intervals.

Alert channels

Email, plain webhooks, n8n and Telegram work on every plan. Slack, Microsoft Teams and Discord need a Business plan. SMS needs a plan that includes it and a confirmed US or Canadian number.

Control

Claude can do only what your Visualping role allows

The connector signs in as you, so Claude never has more access than you do.

Sign-in with an Allow step

You sign in with your Visualping account in the browser and select Allow. There is no API key, and Claude gets no access until you allow it.

Your role is the ceiling

Viewers can read monitors and changes. Editors and Admins can create, change, run and pause them. On Business plans, your role can differ in each workspace.

Read and write tools are labelled

Five tools only read. The other thirteen change something, and Claude may ask you to confirm before it runs them. On Claude Team and Enterprise plans, an Owner can set each tool to Always allow, Needs approval or Blocked.

Saved secrets are not read back to Claude

When Claude reads a monitor's settings, Visualping withholds webhook URLs and the values a monitor types into a page, and names webhook destinations by host only. Add passwords yourself in Visualping's monitor settings, not in the chat.

Get started

Ask Claude for your first monitor

Add Visualping in Claude, sign in, and ask it to watch your first page. A free account is enough to start.

FAQ

Frequently asked questions

Which Visualping plan do I need?

Any plan, including Free. Pages and checks count against the plan you already have. The Free plan checks as often as hourly, and shorter intervals need a paid plan.

Does the connector cost extra?

No. It is included with every Visualping plan and there is no connector fee. Your Claude subscription is separate from your Visualping plan.

Where in Claude does it work?

According to Claude's documentation, connectors from its directory work across Claude on the web, Claude Desktop, Claude Mobile, Claude Code and Cowork. You add the connector under Customize, then Connectors. On Team and Enterprise plans, an organization Owner adds it first and each member then connects with their own account.

I already added Visualping as a custom connector. Do I need to switch?

No. Visualping's server still accepts connectors that were added by URL, including ones on the older /mcp/sse address. For a new setup, the directory listing saves you from pasting a URL.

What can Claude see and do in my Visualping account?

Only what your Visualping role allows, in the workspaces you belong to. On business accounts, it uses your first workspace unless you name another. If you create or join a workspace after connecting, reconnect Visualping in Claude to use it there.

What happens when I reach my plan's limits?

If you run out of checks, monitoring pauses until your monthly allowance resets or you move to a larger plan. If you reach your page limit, the monitors you have keep running, but you cannot start another until you pause one, add pages or change plans.

What can the connector not do yet?

You manage labels, Google Sheets and Google Chat notifications, and user, billing and account settings in the Visualping dashboard. Claude can create, read and change the monitors themselves, including their schedule, page actions and alert destinations.

Does it work in Claude Code?

Yes. Add the Visualping server to Claude Code from your terminal with one command. See the Claude Code integration page for the steps.

Is Visualping affiliated with Anthropic?

No. Visualping is an independent company that builds and maintains this connector. A listing in Claude's Connectors Directory is not an endorsement.

Claude is a trademark of Anthropic, PBC. Visualping is an independent company and is not affiliated with, sponsored by or endorsed by Anthropic.