The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Omniwatchguard MCP listing page.
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.
https://mcp.omniwatchguard.com/mcpEach 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.
| Tool | Description |
|---|---|
list_monitors | List all monitors with recent change activity |
get_monitor | Get full details and the last 20 results for one monitor |
create_monitor | Create a new monitor |
update_monitor | Update an existing monitor's settings |
set_monitor_status | Pause or resume a monitor |
delete_monitor | Delete a monitor |
list_alerts | List recent alerts sent to your account |
Tools need an OmniWatchGuard API key, available on the Pro and Agency plans. Create one in the dashboard and send it as a header:
Listing the tools (initialize, tools/list) works without a key; calling a tool without a key returns an error message.
The same tools are available as a local stdio server, for clients that run MCP servers as a process:
Without OWG_API_KEY the server starts and lists its tools; tool calls return an error message.
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.
MIT, see LICENSE.