Skip to main content
Glama
omniwatchguard-mcp

omniwatchguard-mcp

OmniWatchGuard MCP Server

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.

Related MCP server: uptime-kuma-mcp-server

Tools

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

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

{
  "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 ci
npm run build
OWG_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 ci
npm run deploy

License

MIT, see LICENSE.

Available Tools

7 tools
create_monitorAInspect

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.

Inputs: url (required), name, type, selector, +5 more.

delete_monitorCInspect

Delete an existing monitor.

Inputs: id (required).

get_monitorAInspect

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

Inputs: id (required).

list_alertsBInspect

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

Inputs: type.

list_monitorsAInspect

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

Inputs: no named parameters.

set_monitor_statusCInspect

Pause or resume an existing monitor.

Inputs: id (required), status (required).

update_monitorCInspect

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

Inputs: id (required), url, name, selector, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: CRUD for monitors, one status toggle, and one alert listing. The only potential overlap between update_monitor and set_monitor_status is explicitly resolved by the descriptions (fields vs. pause/resume).

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_monitors, get_monitor, create_monitor, update_monitor, delete_monitor, set_monitor_status). The one deviation, set_monitor_status, is still the same convention with a compound noun.

    Tool Count5/5

    Seven tools is a well-scoped set for a monitor-and-alert service, covering the lifecycle without bloat. Every tool has a clear place in the workflow.

    Completeness4/5

    The surface covers monitor CRUD, pause/resume, and alert listing, which are the core operations. Minor gaps exist, such as no alert acknowledgement/mark-read, no bulk operations, and no check-history retrieval beyond the last 20 results in get_monitor.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables managing Uptime Kuma monitoring through natural language, including creating, editing, pausing, and deleting monitors, plus retrieving heartbeats, status, metrics, notifications, and status pages.
      12
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Uptime monitoring your AI agent can set up: create HTTP, SSL, ping, TCP and DNS monitors checked from multiple regions, run checks on demand, read and acknowledge incidents, manage cron heartbeats, maintenance windows and status page updates.
      57
      1,340 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to manage cron job and scheduled task monitoring through the WatchCron API. Supports listing, creating, updating, pausing, and deleting monitors, retrieving ping URLs and ping/incident history, and listing notification channels.
      9
      11 npm
      MIT