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.
No server URL to paste and no API key to copy.
In Claude, go to Customize, then Connectors, and find Visualping in the directory. The button below opens the listing.
Connect it, sign in with your Visualping account, then select Allow. Claude gets the permissions of your Visualping role and nothing more.
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.
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.
The same Visualping server works in Claude Code, ChatGPT, Codex, Grok, Cursor and VS Code.
Documentation:Claude connectors documentation·Visualping MCP help article
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.
“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.
“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.
“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.
“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.
“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.
These are the same tools Visualping's own assistant uses.
describe_userReadYour account type, plan, check balance, active monitor count and workspaces.
get_monitorsReadLists your monitors, with filters for status and label.
get_monitor_settingsReadThe full setup of one monitor: what it watches, how often, its alert condition, schedule, page actions and alert destinations.
create_monitorWriteStarts watching a URL and runs the first check straight away, with an optional alert condition, page actions and alert destinations.
wait_for_monitor_checkReadWaits 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_monitorWriteRuns a check now instead of waiting for the next scheduled one.
update_monitorWriteChanges a monitor's URL, name, check interval or alert condition.
set_monitor_scheduleWriteLimits checks to a daily time window on the weekdays you choose.
set_monitor_actionsWriteSets steps to run before each capture, such as dismissing a cookie banner or opening a tab.
set_monitor_notificationsWriteChooses where alerts go: email, SMS, Telegram, Slack channels or webhooks.
get_timelineReadDetected changes across your monitors, filtered by monitor, date and importance.
flag_changeWriteFlags a change for follow-up, in a colour if you like.
unflag_changeWriteRemoves a flag.
hide_changeWriteHides a change from the timeline without deleting it.
unhide_changeWriteBrings a hidden change back.
deactivate_monitorWritePauses a monitor and keeps its history.
activate_monitorWriteResumes a paused monitor.
delete_monitorWriteDeletes a monitor and its history for good.
Five tools only read. They never change a monitor.
Thirteen tools change something. Claude may ask you to confirm before it runs one.
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.
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.
Add Visualping in Claude, sign in, and ask it to watch your first page. A free account is enough to start.
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.
No. It is included with every Visualping plan and there is no connector fee. Your Claude subscription is separate from your Visualping plan.
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.
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.
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.
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.
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.
Yes. Add the Visualping server to Claude Code from your terminal with one command. See the Claude Code integration page for the steps.
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.