Omniwatchguard

com.omniwatchguardPublished by omniwatchguard.comOfficial publisherv1.0.0Updated Oct 24, 2026

AI-powered website change monitoring - manage monitors and alerts via MCP.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for OmniWatchGuard that lets an assistant create, inspect, update, pause and delete website change monitors and read recent alerts.

What you can do
  • List monitors with recent change counts and last detected change, and read one monitor's details with its last 20 check results
  • Create monitors for text, price, stock, a CSS-selected element, JSON APIs, SEO fields or SSL certificates
  • Update a monitor's name, URL, selector, check interval or price/stock thresholds
  • Pause, resume or delete monitors
  • List recent alerts sent by email, webhook, Slack, Discord or Telegram with the triggering change
When to use it
Useful when you want to set up or maintain website change tracking from a chat client: watching pages for text, price, stock or API changes, adjusting check intervals and thresholds, and reviewing which changes triggered alerts.
Requirements
Remote Streamable HTTP endpoint at mcp.omniwatchguard.com, or a local stdio build from the repository with Node.js and npm. An OmniWatchGuard API key is required, sent as an Authorization Bearer header (or OWG_API_KEY locally); keys are available on the Pro and Agency plans. Tool listing works without a key, but tool calls fail.
Before you install
The API key is a live credential sent in the Authorization header; keep it out of shared configs and logs. Tools create, modify, pause and delete monitors, so changes affect a real account and its alerting. Monitor count and check intervals depend on the paid plan. The crawler respects robots.txt and does not bypass anti-bot protection, so some sites cannot be monitored.

Installation

In SourceWeft

  1. Open Omniwatchguard in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.omniwatchguard%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "omniwatchguard": {
      "type": "http",
      "url": "https://mcp.omniwatchguard.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

OmniWatchGuard MCP Server

[smithery badge] [Isoprest/omniwatchguard-mcp MCP server]

Model Context Protocol (MCP) server for OmniWatchGuard, a website change monitoring service. Connect Claude, Cursor or any MCP client to your OmniWatchGuard account and manage monitors and alerts in plain language.

  • Endpoint: https://mcp.omniwatchguard.com/mcp
  • Transport: Streamable HTTP (stateless)
  • Authentication: OmniWatchGuard API key, sent as a Bearer token

What you can do

  • List and inspect your monitors
  • Create monitors for text, price, stock, a CSS-selected element, JSON APIs, SEO fields or SSL certificates
  • Change a monitor's URL, selector, check interval or price/stock thresholds
  • Pause, resume or delete monitors
  • Read recent alerts sent by email, webhook, Slack, Discord or Telegram

Each detected change is summarised by an AI model and rated minor, major or critical. Alerts are sent for major and critical changes; minor ones are kept in the history.

Tools

ToolDescription
list_monitorsList all monitors with recent change activity
get_monitorGet full details and the last 20 results for one monitor
create_monitorCreate a new monitor
update_monitorUpdate an existing monitor's settings
set_monitor_statusPause or resume a monitor
delete_monitorDelete a monitor
list_alertsList recent alerts sent to your account

Authentication

Tools need an OmniWatchGuard API key, available on the Pro and Agency plans. Create one in the dashboard and send it as a header:

Authorization: Bearer owg_live_...

Listing the tools (initialize, tools/list) works without a key; calling a tool without a key returns an error message.

Connect from Claude Desktop

json
{  "mcpServers": {    "omniwatchguard": {      "command": "npx",      "args": [        "mcp-remote",        "https://mcp.omniwatchguard.com/mcp",        "--header",        "Authorization: Bearer owg_live_YOUR_KEY_HERE"      ]    }  }}

Run locally (stdio)

The same tools are available as a local stdio server, for clients that run MCP servers as a process:

npm cinpm run buildOWG_API_KEY=owg_live_YOUR_KEY_HERE node dist/stdio.mjs

Without OWG_API_KEY the server starts and lists its tools; tool calls return an error message.

Limits

  • Check intervals: 60 minutes on Starter; 15, 30 or 60 on Pro; 5, 15, 30 or 60 on Agency.
  • The crawler respects robots.txt and does not bypass anti-bot protection. Monitoring works on sites that allow automated access.

Self-hosting

The hosted version is a Cloudflare Worker (src/index.ts) that forwards calls to the OmniWatchGuard API. Both versions share the tools in src/server.ts.

npm cinpm run deploy

License

MIT, see LICENSE.

Source: README.md at commit 59450bb

Tools

7

list_monitors

List all OmniWatchGuard monitors of the authenticated user, with the number of changes in the last 7 days and the last detected change.

Takes no parameters.

get_monitor

Get the full details of one monitor and its last 20 check results.

Parametersidrequired

create_monitor

Create a new monitor for a web page. Types: text, price, stock, css, api, seo, ssl (tech_stack and whois need the matching add-on). The number of monitors and the available check intervals depend on the user's plan.

Parametersurlrequirednametypeselectorfrequencynotify_telegramstock_alert_typeprice_threshold_typeprice_threshold_value

update_monitor

Update fields of an existing monitor: name, URL, selector, check interval or price/stock thresholds.

Parametersidrequiredurlnameselectorfrequencystock_alert_typeprice_threshold_typeprice_threshold_value

set_monitor_status

Pause or resume an existing monitor.

Parametersidrequiredstatusrequired

delete_monitor

Delete an existing monitor.

Parametersidrequired

list_alerts

List the latest alerts sent to the user (email, webhook, Slack, Discord, Telegram), with details of the change that triggered each one.

Parameterstype

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.