Fluxguard integration for multiplayer collaboration with AI agents using Claude Code or Codex

Tool to add a new page for monitoring in FluxGuard. This action can: 1. Create a new site with a page (when siteId/sessionId are not provided) 2. Add a page to an existing site (when siteId/sessionId are provided) When creating a new site, you can optionally assign it to categories and provide a nickname. Use this when you need to start monitoring a URL for changes.

Creates a new site category in FluxGuard for organizing monitored websites. Site categories help you group and manage your monitored sites logically (e.g., by environment like 'Production' or 'Staging', by purpose like 'Marketing' or 'E-commerce', or by client/team). Use this action to create categories before adding sites, making it easier to filter and organize your monitoring dashboard. The returned category ID can be used when adding sites to assign them to this category.

Creates a webhook endpoint registration in FluxGuard to receive real-time notifications when changes are detected on monitored pages. When changes occur, FluxGuard will POST JSON data to your specified URL containing change details, diff information, and file references. Use this when you need to integrate FluxGuard change detection into your own systems, automation workflows, or alerting infrastructure. Note: Only one webhook can be active per account. Creating a new webhook will replace any existing webhook configuration.

Permanently deletes a monitored page from FluxGuard along with all its captured snapshots and version history. This is a destructive operation that cannot be undone. Use this when you need to remove a page that is no longer needed for monitoring. The operation is idempotent - deleting an already-deleted page will succeed without error. To obtain the required IDs (site_id, session_id, page_id), first use FLUXGUARD_ADD_PAGE to create a page or FLUXGUARD_GET_SITES to list existing sites and their pages.

Permanently deletes a monitored site and all associated data including sessions, pages, and captured versions. This operation is idempotent - deleting a non-existent site returns success. Use when you need to remove a site from FluxGuard monitoring.