claude-plugin-wordpress-manager 2.1.1 → 2.2.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "wordpress-manager",
-  "version": "2.1.1",
-  "description": "Unified WordPress management plugin for Claude Code. Orchestrates Hostinger MCP (infrastructure), WP REST API bridge (81 tools incl. WooCommerce + Multisite), and WordPress.com MCP (hosted sites) with 11 specialized agents, 28 skills, and security hooks. Includes site monitoring (uptime, performance baseline, security scanning, content integrity, alerting), CI/CD pipeline automation (GitHub Actions, GitLab CI, Bitbucket), WordPress Multisite network management, WooCommerce store management, local dev environment support, development, testing, security, i18n, accessibility, headless, and operations.",
+  "version": "2.2.0",
+  "description": "Unified WordPress management plugin for Claude Code. Orchestrates Hostinger MCP (infrastructure), WP REST API bridge (85 tools incl. WooCommerce + Multisite + Webhooks), and WordPress.com MCP (hosted sites) with 11 specialized agents, 30 skills, and security hooks. Includes fleet monitoring, content repurposing, webhook propagation, site monitoring (uptime, performance baseline, security scanning, content integrity, alerting), CI/CD pipeline automation (GitHub Actions, GitLab CI, Bitbucket), WordPress Multisite network management, WooCommerce store management, local dev environment support, development, testing, security, i18n, accessibility, headless, and operations.",
   "author": {
     "name": "vinmor",
     "email": "morreale.v@gmail.com"

package/CHANGELOG.md

@@ -2,6 +2,31 @@
 
 All notable changes to the WordPress Manager plugin for Claude Code.
 
+## [2.2.0] - 2026-02-28
+
+### Added
+- **Fleet monitoring** — cross-site health assessment for all configured WordPress sites
+  - New reference file: `skills/wp-monitoring/references/fleet-monitoring.md` (fleet iteration, cross-site patterns, fleet baselines, site grouping, scheduling, P0 escalation)
+  - Detection script updated: `detectFleetConfiguration()` checks WP_SITES_CONFIG and sites.json for multi-site fleet
+  - Agent updated: Procedure 7 (Fleet Monitoring) + Fleet Report Template in `wp-monitoring-agent`
+
+- **Content repurposing skill** (`wp-content-repurposing`) — transform WordPress content into multi-channel outputs
+  - 4 reference files: social-formats (Twitter/LinkedIn/Instagram/Facebook templates), email-newsletter (digest/drip/subject lines), content-atomization (pillar→atoms workflow, repurposing matrix), platform-specs (character limits, image dimensions, posting frequency)
+  - Detection script: `repurposing_inspect.mjs` — detects social plugins, email plugins, content volume
+  - Agent updated: `wp-content-strategist` now includes Content Repurposing Workflow and repurposing example
+
+- **Webhook propagation skill** (`wp-webhooks`) — WordPress outbound webhook configuration and management
+  - 5 reference files: woocommerce-webhooks (API, topics, MCP tools), wordpress-core-webhooks (mu-plugin, action hooks), integration-recipes (Zapier/Make/n8n/Slack/CDN), payload-formats (JSON payloads, WC examples), webhook-security (HMAC-SHA256, signatures, rate limiting)
+  - Detection script: `webhook_inspect.mjs` — detects WC webhooks, mu-plugin webhooks, webhook plugins, wp-config constants
+  - 4 new MCP tools via WP REST Bridge: `wc_list_webhooks`, `wc_create_webhook`, `wc_update_webhook`, `wc_delete_webhook`
+  - `WCWebhook` TypeScript interface added to types.ts
+  - Safety hook for `wc_delete_webhook` (PreToolUse prompt confirmation)
+
+### Changed
+- Router decision-tree.md upgraded to v9 with fleet, webhook, and content repurposing keywords and routing
+- Cross-references added: `wp-content` → wp-content-repurposing, `wp-headless` → wp-webhooks, `wp-woocommerce` → wp-webhooks
+- Plugin now has 30 skills, 11 agents, and 85 MCP tools
+
 ## [2.1.1] - 2026-02-28
 
 ### Changed

package/agents/wp-content-strategist.md

@@ -24,6 +24,13 @@ description: |
   assistant: "I'll use the wp-content-strategist agent to set up the taxonomy structure."
   <commentary>Taxonomy design impacts content architecture and SEO.</commentary>
   </example>
+
+  <example>
+  Context: User wants to repurpose blog content for social media.
+  user: "Turn my latest blog posts into social media content"
+  assistant: "I'll use the wp-content-strategist agent to extract key insights from your posts and generate platform-specific social content."
+  <commentary>Content repurposing requires selecting source content and applying platform templates.</commentary>
+  </example>
 model: inherit
 tools: Read, Grep, Glob, Bash, WebFetch, WebSearch
 ---
@@ -147,6 +154,28 @@ Excerpt: [Meta description with keyword, under 160 chars]
 - ALWAYS preserve existing SEO-optimized slugs when updating content
 - ALWAYS check for duplicate slugs before creating new content
 
+## Content Repurposing Workflow
+
+When repurposing existing WordPress content into multi-channel formats:
+
+1. **Select source content**: Use `list_content` to find recent/popular posts
+   - Filter by `orderby: "date"` for recent or by popularity metrics
+   - Prioritize evergreen content with broad appeal
+2. **Extract key elements** from source post:
+   - Headline and hook
+   - 3-5 key insights or data points
+   - Quotable passages
+   - Statistics or results
+   - Call to action
+3. **Apply platform templates** from `wp-content-repurposing` skill:
+   - Social formats: `references/social-formats.md`
+   - Email newsletter: `references/email-newsletter.md`
+   - Atomization: `references/content-atomization.md`
+4. **Generate formatted outputs** per target channel
+5. **Present all variants** to user for review before distribution
+
+See the `wp-content-repurposing` skill for detailed templates and platform specifications.
+
 ## Multilingual Content
 
 When creating content for multilingual sites:
@@ -164,3 +193,4 @@ When creating content for multilingual sites:
 
 - **`wp-content` skill** — content lifecycle management, editorial workflows
 - **`wp-i18n` skill** — internationalization and localization procedures
+- **`wp-content-repurposing` skill** — content transformation for multi-channel distribution

package/agents/wp-monitoring-agent.md

@@ -24,6 +24,13 @@ description: |
   assistant: "I'll use the wp-monitoring-agent to analyze performance metrics and compare with the baseline."
   <commentary>Performance trend analysis requires collecting current metrics and comparing with historical data.</commentary>
   </example>
+
+  <example>
+  Context: User wants to check all their WordPress sites at once.
+  user: "Run a health check across all my sites"
+  assistant: "I'll use the wp-monitoring-agent to perform a fleet-wide health assessment across all configured sites."
+  <commentary>Fleet monitoring requires iterating over all configured sites and aggregating findings.</commentary>
+  </example>
 model: inherit
 tools: Read, Grep, Glob, Bash, WebFetch, WebSearch
 ---
@@ -109,6 +116,23 @@ Run a full assessment to create a monitoring baseline:
 4. Check robots.txt via WebFetch: verify no unexpected rules
 5. Report content changes, spam levels, and SEO health
 
+### Procedure 7: Fleet Monitoring
+
+Run health assessments across all configured sites and generate a fleet-wide comparison:
+
+1. **Enumerate sites**: Use `list_sites` to get all configured sites
+2. **Iterate**: For each site:
+   a. `switch_site` to target the site
+   b. Run Procedures 3-6 (uptime, performance, security, content)
+   c. Record per-site metrics and findings
+3. **Aggregate**: Combine per-site results into a fleet comparison table
+4. **Cross-site pattern detection**:
+   - Same plugin vulnerability across multiple sites
+   - Correlated performance degradation (shared hosting, CDN issue)
+   - Identical outdated WordPress core versions
+   - Common configuration drift from baselines
+5. **Generate fleet report** (see Fleet Report template below)
+
 ## Report Generation
 
 After completing relevant procedures, generate a report following the templates in `references/reporting-templates.md`:
@@ -155,6 +179,31 @@ After completing relevant procedures, generate a report following the templates
 3. [Third priority]
 ```
 
+### Fleet Report Template
+
+```
+## Fleet Health Report
+**Date:** [date] | **Sites:** [count] | **Scope:** [full / quick]
+
+### Fleet Overview
+| Site | Uptime | Performance | Security | Content | Overall |
+|------|--------|-------------|----------|---------|---------|
+| [site-1] | [✅/⚠️/❌] | [✅/⚠️/❌] | [✅/⚠️/❌] | [✅/⚠️/❌] | [✅/⚠️/❌] |
+| [site-2] | [✅/⚠️/❌] | [✅/⚠️/❌] | [✅/⚠️/❌] | [✅/⚠️/❌] | [✅/⚠️/❌] |
+
+### Fleet Summary
+- **Healthy sites:** X/N
+- **Degraded sites:** X/N (list)
+- **Critical sites:** X/N (list)
+
+### Cross-Site Patterns
+[findings or "No cross-site patterns detected"]
+
+### Fleet Recommendations (Priority Order)
+1. [Fleet-wide action]
+2. [Site-specific action]
+```
+
 ## Safety Rules
 
 - **NEVER modify any site data** — this agent is strictly read-only
@@ -175,6 +224,7 @@ For issues found during monitoring:
 | Content or SEO issues | `wp-content-strategist` agent |
 | Plugin/deployment issues | `wp-deployment-engineer` agent |
 | Infrastructure/hosting issues | `wp-site-manager` agent |
+| Fleet-wide infrastructure issue | `wp-site-manager` agent (multi-site coordination) |
 
 ## Related Skills
 

package/docs/plans/2026-02-28-wcop-strategic-assessment.md

@@ -0,0 +1,220 @@
+# WordPress Manager — Assessment Strategico WCOP
+
+> **WordPress Content Orchestration Platform (WCOP)**
+> Valutazione del plugin v2.1.1 come piattaforma di orchestrazione per content management distribuito a supporto di strategie SEO, engagement e social amplification.
+
+**Data:** 2026-02-28
+**Versione plugin:** 2.1.1
+**Scope:** Alto livello strategico — nessuna implementazione
+
+---
+
+## 1. Modello di Riferimento: WCOP a 5 Layer
+
+Il plugin v2.1.1 va valutato non come "gestore di siti WordPress" ma come **piattaforma di orchestrazione contenuti** strutturata su 5 livelli:
+
+```
+Layer 5 ─ Automation     CI/CD pipeline, webhook, trigger
+Layer 4 ─ Observability  Monitoring, baseline, alerting
+Layer 3 ─ Distribution   Headless, syndication, social, email
+Layer 2 ─ Quality Assur. Testing, security, accessibility, PHPStan
+Layer 1 ─ Content Factory Multisite, WooCommerce, REST API, block dev
+```
+
+### Punteggi per Layer
+
+| Layer | Copertura | Score | Note |
+|-------|-----------|-------|------|
+| 1 — Content Factory | Eccellente | **9/10** | 81 tool MCP, 28 skill, multisite, WooCommerce, headless skill |
+| 2 — Quality Assurance | Forte | **8/10** | E2E + PHPStan + security audit + a11y + hardening |
+| 3 — Distribution | **Debole** | **4/10** | Solo headless skill teorico, nessun connettore outbound reale |
+| 4 — Observability | Parziale | **5/10** | Monitoring single-site, manca fleet monitoring cross-site |
+| 5 — Automation | Parziale | **4/10** | CI/CD per codice, non per contenuto; manca webhook propagation |
+
+**Score complessivo: 6/10** — Il plugin e forte **centripetalmente** (portare contenuto DENTRO WordPress) ma debole **centrifugalmente** (distribuire contenuto FUORI DA WordPress).
+
+---
+
+## 2. Hub Content Architecture
+
+Il plugin ha la base per un modello **Hub-and-Spoke**:
+
+- **Hub**: WordPress Multisite (10 tool MCP) come sorgente canonica
+- **Spoke**: Frontend headless via `wp-headless` skill (REST/WPGraphQL -> Next.js/Nuxt/Astro)
+- **Commerce layer**: WooCommerce (30 tool MCP) come transazione integrata
+
+**Punto di forza**: L'orchestrazione `wp-site-manager` -> delegazione a 10 agent specializzati e un pattern raro nel panorama plugin CLI. La catena audit->hardening (`wp-security-auditor` -> `wp-security-hardener`) e la delegazione monitor->specialist (`wp-monitoring-agent` -> performance/security agent) sono differenzianti.
+
+**Gap**: L'hub e forte nella creazione ma non nella propagazione. Il contenuto nasce in WordPress e li resta.
+
+---
+
+## 3. SEO Topology
+
+| Strategia SEO | Supporto | Dettaglio |
+|---------------|----------|-----------|
+| Pillar-Cluster | ✅ Forte | Content strategist + REST API categories/tags + headless rendering |
+| E-Commerce SEO | ✅ Forte | WooCommerce products + structured data via headless |
+| Programmatic SEO | ⚠️ Parziale | Headless skill copre il pattern, ma manca generazione template scalabile |
+| Local SEO (multi-location) | ⚠️ Parziale | Multisite permette siti per location, manca schema LocalBusiness |
+| Cross-Domain SEO | ❌ Assente | Nessun tool per canonical cross-domain, hreflang fleet, o link graph |
+
+**Opportunita chiave**: Programmatic SEO tramite headless + Multisite e a portata di mano. Un sito multisite dove ogni sub-site genera pagine programmatiche (es. "/prodotto/citta/variante") con Next.js ISR sarebbe potente.
+
+---
+
+## 4. Content Syndication
+
+| Livello | Descrizione | Supporto |
+|---------|-------------|----------|
+| L1 — Canonical Source | WordPress come sorgente unica di verita | ✅ Eccellente (REST API, WPGraphQL) |
+| L2 — Format Adaptation | Trasformare contenuto per canali diversi | ⚠️ Solo manuale (content strategist) |
+| L3 — Channel Distribution | Pubblicare su social, email, ads, partner | ❌ Assente |
+
+Il plugin produce contenuto strutturato di alta qualita (L1) ma non ha pipeline per riformattarlo (L2) ne distribuirlo (L3). Il contenuto "muore" dentro WordPress.
+
+---
+
+## 5. Commerce-Content Integration
+
+WooCommerce e ben integrato (30 tool) ma come layer **transazionale**, non come layer **content-driven**:
+
+- **Content -> Commerce** ⚠️: Si possono creare prodotti e gestire ordini, ma manca il funnel content->conversion tracking
+- **Commerce -> Content** ⚠️: I dati vendita (report WC) esistono ma non alimentano automaticamente la strategia contenuti
+- **Headless Commerce** ⚠️: `wp-headless` skill copre la teoria ma non c'e un workflow "WooCommerce headless" dedicato
+
+---
+
+## 6. Social Amplification
+
+**Posizione corretta del plugin**: Non deve diventare un social media manager (esistono tool dedicati). Deve essere il **miglior fornitore di contenuto strutturato** per tool di distribuzione esterni.
+
+Cio significa: API-first content packaging. WordPress produce JSON strutturato (titolo, excerpt, immagini ottimizzate, categorie, schema markup) che un tool esterno (Buffer, Hootsuite, Zapier) può consumare.
+
+**Gap**: Manca un layer di "content packaging for distribution" — endpoint REST dedicati che formattino il contenuto per i vari canali.
+
+---
+
+## 7. Monitoring come Quality Gate + CI/CD come Content Pipeline
+
+### Monitoring (Differenziante)
+
+Il monitoring v2.1.0 e un **differenziante unico**: nessun altro plugin CLI offre monitoring integrato con delegazione a agent specializzati. La catena:
+
+```
+wp-monitoring-agent (detect anomaly)
+  -> wp-performance-optimizer (if performance issue)
+  -> wp-security-auditor (if security issue)
+  -> wp-site-manager (if infrastructure issue)
+```
+
+Questo pattern va **esteso a fleet level**: monitorare N siti simultaneamente, aggregare metriche, identificare pattern cross-site.
+
+### CI/CD come Content Pipeline (Innovativo)
+
+L'insight piu interessante: CI/CD non dovrebbe essere solo per codice ma anche per **contenuto**:
+
+- Quality gate su contenuti (SEO score minimo, a11y check, reading level)
+- Preview environment per contenuto (staging -> produzione)
+- Rollback contenuto (versioning via REST API revisions)
+
+Il plugin ha gia `wp-cicd-engineer` per codice. Estenderlo a "content pipeline" sarebbe innovativo.
+
+---
+
+## 8. Gap Analysis — Roadmap Strategica
+
+### Tier 1 — Alto Impatto, Alta Fattibilita
+
+| Gap | Descrizione | Effort | Impatto |
+|-----|-------------|--------|---------|
+| **Fleet Monitoring** | Estendere monitoring a N siti (loop su sites.json) | Medio | Trasforma il plugin da single-site a network operator |
+| **Content Repurposing Skill** | Skill che guida la trasformazione contenuto->formati (social post, email, snippet) | Basso | Sblocca L2 syndication |
+| **Webhook Propagation** | Skill/tool per configurare webhook WordPress -> servizi esterni | Basso | Primo mattone per distribuzione automatica |
+
+### Tier 2 — Alto Impatto, Media Fattibilita
+
+| Gap | Descrizione | Effort | Impatto |
+|-----|-------------|--------|---------|
+| **Programmatic SEO Skill** | Generazione template pagine scalabili (headless + multisite) | Medio | SEO topology massiva |
+| **Content-Commerce Attribution** | Collegare metriche WooCommerce a contenuti che generano conversioni | Medio | ROI content misurabile |
+| **Multi-Language Network** | Orchestrazione multisite multilingua (hreflang, i18n + multisite) | Alto | Sblocca mercati internazionali |
+
+### Tier 3 — Alto Impatto, Richiede Ecosistema
+
+| Gap | Descrizione | Effort | Impatto |
+|-----|-------------|--------|---------|
+| **Social/Email Connectors** | MCP tool per Mailchimp, Buffer, etc. (o Zapier bridge) | Alto | L3 distribution completa |
+| **Google Search Console Integration** | MCP tool per GSC API (keyword tracking, indexing) | Medio | SEO feedback loop |
+| **AI Content Optimization** | Skill per ottimizzazione contenuto con AI (headline testing, readability) | Medio | Content quality automatica |
+
+---
+
+## 9. Modello d'Impiego Massimizzato
+
+### Scenario: "Content Hub Distribuito per Brand D2C"
+
+Esempio concreto di impiego simultaneo massimale del plugin:
+
+```
+                    ┌─────────────────────┐
+                    │  WORDPRESS MULTISITE │
+                    │    (Hub Centrale)    │
+                    │   wp-site-manager    │
+                    └──────────┬──────────┘
+           ┌───────────────────┼───────────────────┐
+           │                   │                   │
+    ┌──────▼──────┐    ┌──────▼──────┐    ┌──────▼──────┐
+    │  Sub-site 1 │    │  Sub-site 2 │    │  Sub-site 3 │
+    │  Blog/SEO   │    │ WooCommerce │    │   Landing   │
+    │  (content)  │    │   (shop)    │    │  (campaign) │
+    └──────┬──────┘    └──────┬──────┘    └──────┬──────┘
+           │                   │                   │
+    ┌──────▼──────┐    ┌──────▼──────┐    ┌──────▼──────┐
+    │  Next.js    │    │  Nuxt.js    │    │  Astro      │
+    │  (headless) │    │  (headless) │    │  (static)   │
+    └─────────────┘    └─────────────┘    └─────────────┘
+```
+
+**Agent attivi simultaneamente:**
+
+1. `wp-content-strategist` — crea contenuto pillar nel sub-site blog
+2. `wp-ecommerce-manager` — gestisce catalogo e promozioni nel sub-site shop
+3. `wp-cicd-engineer` — mantiene pipeline deploy per i 3 frontend headless
+4. `wp-monitoring-agent` — sorveglia uptime e performance di tutti i sub-siti
+5. `wp-security-auditor` + `wp-security-hardener` — ciclo audit/hardening periodico
+6. `wp-test-engineer` — E2E testing sui frontend headless
+7. `wp-accessibility-auditor` — compliance WCAG sui frontend pubblici
+
+**Skill attive:**
+
+- `wp-multisite` per gestione rete
+- `wp-headless` per configurazione API layer
+- `wp-woocommerce` per store operations
+- `wp-cicd` per pipeline automation
+- `wp-monitoring` per observability
+- `wordpress-router` per orchestrazione decisionale
+
+> Questo scenario usa **7 degli 11 agent** e **6 delle 28 skill** simultaneamente.
+
+---
+
+## 10. Conclusione Strategica
+
+Il plugin WordPress Manager v2.1.1 e una **piattaforma di orchestrazione contenuti matura al 60%**:
+
+- **Eccellente** come Content Factory (Layer 1) e Quality Assurance (Layer 2)
+- **Differenziante** nel pattern monitoring->delegazione e nella copertura agent (11 specializzati)
+- **Carente** nella distribuzione outbound (Layer 3) e nell'automazione contenuto (Layer 5)
+
+### La trasformazione da "gestore WordPress" a "Content Orchestration Platform" richiede 3 mosse strategiche:
+
+1. **Fleet-first**: Ogni tool e agent deve pensare "N siti", non "1 sito"
+2. **Content-out**: Aggiungere il layer di distribuzione (content packaging -> webhook -> canali)
+3. **Content pipeline**: Estendere CI/CD dal codice al contenuto (quality gates, staging, rollback)
+
+Con queste 3 evoluzioni, il plugin passerebbe da **6/10 a 8-9/10** come piattaforma WCOP, posizionandosi come l'unico strumento CLI che copre l'intero ciclo di vita del contenuto WordPress: **creazione -> qualita -> distribuzione -> osservabilita -> automazione**.
+
+---
+
+*Assessment WCOP v1.0 — wordpress-manager v2.1.1 — 2026-02-28*

package/hooks/hooks.json

@@ -51,6 +51,15 @@
             "timeout": 15
           }
         ]
+      },
+      {
+        "matcher": "mcp__wp-rest-bridge__wc_delete_webhook",
+        "hooks": [
+          {
+            "type": "prompt",
+            "prompt": "The agent is about to DELETE a WooCommerce webhook. This will stop notifications to the configured delivery URL. Verify the user explicitly requested this deletion and understands that external integrations depending on this webhook will stop receiving events."
+          }
+        ]
       }
     ]
   }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "claude-plugin-wordpress-manager",
-  "version": "2.1.1",
-  "description": "Unified WordPress management and development plugin for Claude Code. Orchestrates Hostinger MCP, WP REST API bridge (81 tools incl. 30 WooCommerce + 10 Multisite), and WordPress.com MCP with 28 skills, 11 agents, and security hooks. v2.1.0 adds site monitoring: uptime checks, performance baseline, security scanning, content integrity, alerting strategies, and reporting templates.",
+  "version": "2.2.0",
+  "description": "Unified WordPress management and development plugin for Claude Code. Orchestrates Hostinger MCP, WP REST API bridge (85 tools incl. 30 WooCommerce + 10 Multisite + 4 Webhooks), and WordPress.com MCP with 30 skills, 11 agents, and security hooks. v2.2.0 adds fleet monitoring, content repurposing skill, and webhook propagation (WooCommerce webhook MCP tools + mu-plugin patterns).",
   "author": {
     "name": "vinmor",
     "email": "morreale.v@gmail.com"
@@ -33,7 +33,10 @@
     "gitlab-ci",
     "monitoring",
     "uptime",
-    "health-check"
+    "health-check",
+    "webhook",
+    "content-repurposing",
+    "fleet-monitoring"
   ],
   "repository": {
     "type": "git",

package/servers/wp-rest-bridge/build/tools/index.d.ts

@@ -1,6 +1,125 @@
 import { Tool } from '@modelcontextprotocol/sdk/types.js';
 export declare const allTools: Tool[];
 export declare const toolHandlers: {
+    wc_list_webhooks: (params: import("zod").TypeOf<import("zod").ZodObject<{
+        status: import("zod").ZodOptional<import("zod").ZodEnum<["active", "paused", "disabled"]>>;
+    }, "strict", import("zod").ZodTypeAny, {
+        status?: "active" | "paused" | "disabled" | undefined;
+    }, {
+        status?: "active" | "paused" | "disabled" | undefined;
+    }>>) => Promise<{
+        toolResult: {
+            content: {
+                type: string;
+                text: string;
+            }[];
+            isError?: undefined;
+        };
+    } | {
+        toolResult: {
+            isError: boolean;
+            content: {
+                type: string;
+                text: string;
+            }[];
+        };
+    }>;
+    wc_create_webhook: (params: import("zod").TypeOf<import("zod").ZodObject<{
+        name: import("zod").ZodString;
+        topic: import("zod").ZodString;
+        delivery_url: import("zod").ZodString;
+        secret: import("zod").ZodOptional<import("zod").ZodString>;
+        status: import("zod").ZodOptional<import("zod").ZodEnum<["active", "paused", "disabled"]>>;
+    }, "strict", import("zod").ZodTypeAny, {
+        name: string;
+        topic: string;
+        delivery_url: string;
+        status?: "active" | "paused" | "disabled" | undefined;
+        secret?: string | undefined;
+    }, {
+        name: string;
+        topic: string;
+        delivery_url: string;
+        status?: "active" | "paused" | "disabled" | undefined;
+        secret?: string | undefined;
+    }>>) => Promise<{
+        toolResult: {
+            content: {
+                type: string;
+                text: string;
+            }[];
+            isError?: undefined;
+        };
+    } | {
+        toolResult: {
+            isError: boolean;
+            content: {
+                type: string;
+                text: string;
+            }[];
+        };
+    }>;
+    wc_update_webhook: (params: import("zod").TypeOf<import("zod").ZodObject<{
+        id: import("zod").ZodNumber;
+        name: import("zod").ZodOptional<import("zod").ZodString>;
+        topic: import("zod").ZodOptional<import("zod").ZodString>;
+        delivery_url: import("zod").ZodOptional<import("zod").ZodString>;
+        secret: import("zod").ZodOptional<import("zod").ZodString>;
+        status: import("zod").ZodOptional<import("zod").ZodEnum<["active", "paused", "disabled"]>>;
+    }, "strict", import("zod").ZodTypeAny, {
+        id: number;
+        status?: "active" | "paused" | "disabled" | undefined;
+        name?: string | undefined;
+        topic?: string | undefined;
+        delivery_url?: string | undefined;
+        secret?: string | undefined;
+    }, {
+        id: number;
+        status?: "active" | "paused" | "disabled" | undefined;
+        name?: string | undefined;
+        topic?: string | undefined;
+        delivery_url?: string | undefined;
+        secret?: string | undefined;
+    }>>) => Promise<{
+        toolResult: {
+            content: {
+                type: string;
+                text: string;
+            }[];
+            isError?: undefined;
+        };
+    } | {
+        toolResult: {
+            isError: boolean;
+            content: {
+                type: string;
+                text: string;
+            }[];
+        };
+    }>;
+    wc_delete_webhook: (params: import("zod").TypeOf<import("zod").ZodObject<{
+        id: import("zod").ZodNumber;
+    }, "strict", import("zod").ZodTypeAny, {
+        id: number;
+    }, {
+        id: number;
+    }>>) => Promise<{
+        toolResult: {
+            content: {
+                type: string;
+                text: string;
+            }[];
+            isError?: undefined;
+        };
+    } | {
+        toolResult: {
+            isError: boolean;
+            content: {
+                type: string;
+                text: string;
+            }[];
+        };
+    }>;
     ms_list_network_plugins: (params: import("zod").TypeOf<import("zod").ZodObject<{
         site_id: import("zod").ZodOptional<import("zod").ZodString>;
     }, "strict", import("zod").ZodTypeAny, {

package/servers/wp-rest-bridge/build/tools/index.js

@@ -14,6 +14,7 @@ import { wcReportTools, wcReportHandlers } from './wc-reports.js';
 import { wcSettingTools, wcSettingHandlers } from './wc-settings.js';
 import { multisiteSiteTools, multisiteSiteHandlers } from './multisite-sites.js';
 import { multisiteNetworkTools, multisiteNetworkHandlers } from './multisite-network.js';
+import { wcWebhookTools, wcWebhookHandlers } from './wc-webhooks.js';
 // Combine all tools
 export const allTools = [
     ...unifiedContentTools, // 8 tools
@@ -32,6 +33,7 @@ export const allTools = [
     ...wcSettingTools, // 4 tools
     ...multisiteSiteTools, // 5 tools
     ...multisiteNetworkTools, // 5 tools
+    ...wcWebhookTools, // 4 tools
 ];
 // Combine all handlers
 export const toolHandlers = {
@@ -51,4 +53,5 @@ export const toolHandlers = {
     ...wcSettingHandlers,
     ...multisiteSiteHandlers,
     ...multisiteNetworkHandlers,
+    ...wcWebhookHandlers,
 };