Add the Visualping MCP server to Claude Code and ask it to watch any page. Visualping keeps checking from its own servers after the session ends, and every change comes back with a Visualping AI summary.
One command, one browser sign-in, and no API key to copy.
Run this in your terminal. By default the server is saved for the current project only. Add --scope user to load it in every project, or --scope project to write a .mcp.json file your team can commit.
claude mcp add --transport http visualping https://visualping.io/mcpStart Claude Code, run /mcp, select visualping and follow the browser sign-in, or run the command below. Log in to visualping.io and click Allow. Claude gets the permissions of your Visualping role and nothing more.
claude mcp login visualpingDescribe the page and what matters. Claude creates the monitor, and Visualping checks it on schedule from its own servers, whether or not Claude Code is still open.
Watch https://competitor.example/pricing daily and flag it when a price changes.Add this to the .mcp.json file in your project root and restart Claude Code. The entry needs the type field: Claude Code reads a URL without one as a local server.
{
"mcpServers": {
"visualping": {
"type": "http",
"url": "https://visualping.io/mcp"
}
}
}The same server works as a custom connector. Open Connectors in your Claude settings, choose Add custom connector, paste the server URL and sign in with your Visualping account.
https://visualping.io/mcpDocumentation:Claude Code MCP documentation·Visualping MCP help article
Each request maps to a Visualping MCP tool, and Claude only gets the permissions your Visualping role allows.
“Watch this pricing page every day and alert me only if a price drops below $500.”
Creates a monitor with a plain-English alert condition. Visualping AI reads each change against it and flags the ones that matter.
“What changed on my monitors this week?”
Reads the change timeline, with the Visualping AI summary and Important flag for each event, so Claude can answer without opening a screenshot.
“Check it now and tell me what you see.”
Triggers an immediate check, waits for the capture, and reports what the page showed.
“Send alerts from the pricing monitors to this webhook instead of email.”
Changes where a monitor sends its alerts, from email and webhooks to Slack, Microsoft Teams, Discord, Telegram, SMS and n8n, within what your plan includes.
“Dismiss the cookie banner and open the Pricing tab before each check.”
Sets the page actions 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 staging monitors.”
Restricts checks to a daily window in your account's time zone, and pauses monitors while keeping their history.
Claude Code can reason and write code, but it needs a durable place to put a watch. Visualping is that place.
Keeps watching after the session ends
Visualping checks the page on its own schedule from its own servers. There is no polling loop to write and no cron job for the agent to maintain.
Every change comes with a Visualping AI summary
Each change event carries a summary and an Important flag, so Claude can read what moved without opening screenshots. Describe what matters in plain English to tune the alerts.
Your sign-in, your permissions
OAuth sign-in with your Visualping account, with nothing to paste into a config file. Claude can only do what your Visualping role allows, in the workspaces you belong to.
Works on every plan, including Free
There are no separate MCP limits. Checks and pages count against the plan you already have, so you can start with a free account.
Install the public Visualping API skill. It teaches Claude Code the Visualping REST API, generates ready-to-run curl, Python and JavaScript snippets, and can call the API directly with your key.
Create a free Visualping account, add the server, and ask Claude to watch your first page.
No. The Visualping MCP server uses OAuth. You sign in with your Visualping account in the browser and click Allow. API keys are only needed for the REST API.
Any plan, including Free. There are no separate MCP limits. Checks and pages count against your plan's normal quota. The Free plan checks hourly at most, and shorter intervals need a paid plan.
No. You add it as a custom server by URL, with the command above or under Connectors in Claude. Claude Code treats it like any other remote MCP server.
Yes. Add https://visualping.io/mcp as a custom connector in your Claude settings and sign in with your Visualping account. On Team and Enterprise plans, an admin may need to add it for the organization.
Labels, Google Sheets notifications, and user, billing and account settings are managed in the Visualping dashboard. Monitors themselves, including their schedule, page actions and alert destinations, can be created, read and changed from Claude Code.
As often as your plan allows. The Free plan checks as often as hourly, and paid plans unlock shorter intervals. Claude can also trigger a check right away instead of waiting for the next scheduled run.
Claude, ChatGPT and Grok are supported, and OpenAI Codex works with the same server. Other clients that support remote MCP servers with OAuth sign-in can connect by URL. See the OpenAI integration page for ChatGPT and Codex setup.