# Isoprest/omniwatchguard-mcp [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/Isoprest/omniwatchguard-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-234

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

## Tools
Capabilities this server exposes over MCP:

- **list_monitors** — List all monitors with recent change activity
- **get_monitor** — Get full details and recent 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 notifications sent to your account

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "omniwatchguard-mcp": {
    "url": "https://mcp.omniwatchguard.com/mcp"
  }
}
```

## Documentation

## What Isoprest/omniwatchguard-mcp MCP server does

Isoprest/omniwatchguard-mcp MCP server exposes OmniWatchGuard account operations as MCP tools. It is intended for managing website monitors and checking the notifications those monitors have generated. Agents can retrieve monitor lists, inspect an individual monitor and its recent results, create monitors, change their settings, change their running state, or remove them.

The underlying OmniWatchGuard service supports monitors for several kinds of website changes, including prices, inventory availability, text, visual appearance, CSS, API responses, and SEO-related changes. The server does not create a separate monitoring system; it provides an MCP interface to an existing OmniWatchGuard account.

## How it works

The service is available at `https://mcp.omniwatchguard.com/mcp` using Streamable HTTP. An MCP client connects to that endpoint and sends an OmniWatchGuard API key as a Bearer authorization header. Once authenticated, the agent can call the server’s monitor and alert tools according to the requested operation.

The available operations are split between monitor administration and alert review. Monitor tools return current or recent monitor information and support lifecycle changes. The alert tool lists recent notifications sent to the account, including notifications delivered through supported channels such as email, Slack, Discord, Telegram, and webhooks.

## Setup and configuration

Isoprest/omniwatchguard-mcp requires an OmniWatchGuard API key from a Pro plan or higher. Generate the key in the OmniWatchGuard dashboard and provide it in this form:

```text
Authorization: Bearer owg_live_YOUR_KEY_HERE
```

For Claude Desktop, the README shows a configuration that runs `mcp-remote` through `npx` and passes the remote endpoint and authorization header as arguments:

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

The supplied material documents header-based authentication rather than environment-variable configuration. Protect the API key when placing it in a client configuration.

## Tools and capabilities

Isoprest/omniwatchguard-mcp MCP server provides these tools:

- `list_monitors` retrieves all monitors with recent change activity.
- `get_monitor` returns detailed information and recent results for one monitor.
- `create_monitor` adds a new monitor.
- `update_monitor` changes an existing monitor’s settings, including documented frequency, threshold, and selector settings.
- `set_monitor_status` pauses or resumes a monitor.
- `delete_monitor` removes a monitor.
- `list_alerts` returns recent notifications sent to the account.

These capabilities fit workflows where an agent needs to review monitoring state, adjust monitoring rules, or examine recent account alerts without switching to the OmniWatchGuard dashboard.

## Limitations and notes

Access requires an OmniWatchGuard API key and a Pro plan or higher. The server depends on the remote OmniWatchGuard Streamable HTTP endpoint, so the client must support MCP connections through that endpoint or use a compatible bridge such as `mcp-remote`. The provided material documents Claude Desktop and Cursor as connection options, but does not specify additional client-specific setup.

The available tool list covers monitor and alert management. It does not document tools for configuring notification destinations, viewing historical data beyond the returned recent results or alerts, or changing OmniWatchGuard account billing and plan settings.

_Full upstream README: https://allmcps.com/mcp/mcp-234/readme_