VisualPing MCP server for your Slack AI agent

Integrate VisualPing MCP server into your Slack workspace for instant access to your AI agent.

Back to MCP Servers
VisualPing
VisualPing
Website change detection, monitoring and alerting

Categories

Web & App Development

Available Tools

Tools that your AI agent can use through this MCP server to interact with VisualPing

Update Job

Updates one or more settings of an existing Visualping job — schedule, trigger, notification config, crop region, and more. Only the fields you pass are changed; everything else on the job stays as-is. Use Find Jobs or Get Job Details By Id first to confirm the jobId and current settings if you're not certain which job the user means. Example: to pause a noisy job, call with just jobId="482913" and active=false → returns the updated job object with active: false. See the documentation

List Workspace ID Options

Discovers the valid workspaceId (and, for business/team accounts, organisationId) values for the connected Visualping account. Call this first before any tool that takes a workspaceId or organisationId prop — never guess those ids. Example: call with no arguments → returns { workspaces: [{id, name}, ...], organisation: {id, name} }. On a personal-tier account workspaces is typically empty and organisation is omitted entirely — that's expected, not an error. See the documentation

Get Job Details By Id

Gets the full details of one Visualping job by id — schedule, trigger, notification config, crop region, and change-detection history. Use Find Jobs first to locate the job id if you don't already have it. Example: to confirm a job's check interval after creating it, call with the jobId returned by Create A New Job → returns the full job object including interval, trigger, mode, and active. Pass fields to return only the fields you need. See the documentation

Find Jobs

Searches and lists your Visualping monitoring jobs, with optional filters for mode, active/paused state, change-detection frequency, and free text. Use this to discover job ids before calling Get Job Details By Id, Update Job, or Delete Job, or to answer questions like "which jobs are still active" or "find the job monitoring example.com". Auto-paginates through the API's 100-jobs-per-page results, up to a cap of 20 pages (2,000 jobs) — plenty for typical accounts. Example: to find active jobs mentioning "pricing", call with fullTextSearchFilter="pricing" and activeFilter=true → returns matching job records with id, url, mode, interval, trigger, isActive, and more. Pass fields to shrink each result to just the fields you need. See the documentation

Delete Job

Permanently deletes a Visualping job by id. This stops monitoring and cannot be undone — use Find Jobs first to confirm you have the right jobId before calling this, especially if the user described the job by name or URL rather than by id. Example: after confirming job 482913 is the one monitoring https://example.com/pricing, call with jobId="482913" → the job stops being checked and no longer appears in Find Jobs. See the documentation

Create A New Job

Creates a new Visualping monitoring job that checks a web page on a schedule and alerts on a detected change. Use for requests like "monitor this page for changes" or "watch this URL and tell me when the price changes". Set active: false to create the job paused (useful for testing before it starts consuming your plan's active-job quota). Example: to watch a pricing page for any change every hour, call with url="https://example.com/pricing", mode="VISUAL", interval="60", trigger="5", targetDevice="4", active=true → returns the created job object with its new id, which you'll need for Get Job Details By Id, Update Job, or Delete Job. For mode="TEXT" jobs, also set keywordAction and keywords to watch for specific text changes. For AREA crawling (targetDevice 1 or 3), also set cropX/cropY/cropWidth/cropHeight. See the documentation