@nightsquawktech/proxmox-mcp-server 0.1.0

package/dist/catalog-pve/enrichment/delete_cluster_notifications_endpoints_webhook_name.json

@@ -0,0 +1,25 @@
+{
+  "operationId": "delete_cluster_notifications_endpoints_webhook_name",
+  "usageNotes": "Permanently removes a webhook notification endpoint from the cluster by its config ID. The endpoint must not be referenced by any active notification matchers or rules — removing a webhook that is still in use by a matcher will leave those matchers in a broken state. Requires the Mapping.Modify privilege on /mapping/notifications.",
+  "examples": [
+    {
+      "summary": "Delete a webhook endpoint named 'alerts-webhook'",
+      "path_params": {
+        "name": "alerts-webhook"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently deletes the webhook endpoint configuration; any notification matchers still referencing this endpoint will silently fail to deliver alerts.",
+  "tips": [
+    "Check active notification matchers with GET /cluster/notifications/matchers before deleting to avoid silent alert delivery failures.",
+    "The name must match a pve-configid — alphanumeric with hyphens/underscores, no spaces.",
+    "Returns null on success; a 4xx error indicates the endpoint does not exist or a permission failure."
+  ],
+  "relatedOperations": [
+    "get_cluster_notifications_endpoints_webhook_name",
+    "create_cluster_notifications_endpoints_webhook",
+    "update_cluster_notifications_endpoints_webhook_name",
+    "get_cluster_notifications_matchers"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_notifications_matchers_name.json

@@ -0,0 +1,26 @@
+{
+  "operationId": "delete_cluster_notifications_matchers_name",
+  "usageNotes": "Permanently removes a notification matcher from the cluster. Matchers define routing rules that link notification events to targets; deleting one silently drops all routing rules it contained, so any notifications previously matched by it will fall back to other matchers or go undelivered. Requires Mapping.Modify on /mapping/notifications at the cluster level.",
+  "examples": [
+    {
+      "summary": "Delete the matcher named 'high-priority-alerts'",
+      "path_params": {
+        "name": "high-priority-alerts"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently removes the matcher and all its routing rules; any notification events that relied on this matcher will no longer be delivered to their associated targets.",
+  "tips": [
+    "Matcher names follow the pve-configid format: lowercase alphanumeric and hyphens only.",
+    "There is no soft-delete or recycle bin — deletion is immediate and irreversible via the API.",
+    "Before deleting, review which notification targets depend on this matcher using the GET /cluster/notifications/matchers/{name} endpoint to avoid silent notification gaps.",
+    "Returns null on success; a non-null error response indicates the matcher does not exist or a permission issue."
+  ],
+  "relatedOperations": [
+    "get_cluster_notifications_matchers_name",
+    "create_cluster_notifications_matchers",
+    "update_cluster_notifications_matchers_name",
+    "get_cluster_notifications_matchers"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_qemu_custom_cpu_models_cputype.json

@@ -0,0 +1,24 @@
+{
+  "operationId": "delete_cluster_qemu_custom_cpu_models_cputype",
+  "usageNotes": "Permanently removes a custom CPU model definition from the cluster. The caller must hold Mapping.Modify on /mapping/cpu/{cputype}. Any VM or template already configured with this CPU type will retain the reference in its config but Proxmox will be unable to resolve the model on next start — remove or retype those VMs before deleting the model.",
+  "examples": [
+    {
+      "summary": "Delete the custom CPU model 'custom-epyc-v4-tuned'",
+      "path_params": {
+        "cputype": "custom-epyc-v4-tuned"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "The custom CPU model definition is permanently erased from the cluster; any VM referencing it will fail to start until its CPU type is updated.",
+  "tips": [
+    "The 'custom-' prefix in the cputype value is optional — 'epyc-v4-tuned' and 'custom-epyc-v4-tuned' both resolve to the same model.",
+    "Check which VMs reference this model with get_cluster_qemu_custom_cpu_models or by scanning VM configs before deleting.",
+    "Returns null on success — no UPID is issued; the deletion is synchronous."
+  ],
+  "relatedOperations": [
+    "get_cluster_qemu_custom_cpu_models",
+    "create_cluster_qemu_custom_cpu_models",
+    "update_cluster_qemu_custom_cpu_models_cputype"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_replication_id.json

@@ -0,0 +1,28 @@
+{
+  "operationId": "delete_cluster_replication_id",
+  "usageNotes": "Marks a replication job for removal and, by default, cleans up the replicated snapshots on the target. Use `force=true` to remove only the job configuration immediately without waiting for or performing cleanup — useful when the target is unreachable. Use `keep=true` to leave replicated data on the target intact (e.g., when repurposing the replica). Requires VM.Replicate on the guest's /vms/<vmid> path.",
+  "examples": [
+    {
+      "summary": "Delete replication job 105-0, cleaning up replicated data on the target",
+      "path_params": {
+        "id": "105-0"
+      },
+      "params": {
+        "force": false,
+        "keep": false
+      }
+    }
+  ],
+  "destructiveReason": "Permanently removes the replication job configuration and, unless `keep=true` is set, deletes the replicated snapshots from the target node — removing the offsite copy of the guest.",
+  "tips": [
+    "If the target node is offline or unreachable, use `force=true` to remove the job config without attempting cleanup; manually remove leftover snapshots on the target later.",
+    "Set `keep=true` when you want to promote the replica (e.g., the source was destroyed) — the replicated snapshots remain and can be used to restore or migrate the guest.",
+    "The job ID format is '<VMID>-<JOBNUM>' (e.g., '105-0'); VMID must be 3–9 digits starting with 1–9, and JOBNUM 1–9 digits."
+  ],
+  "relatedOperations": [
+    "get_cluster_replication_id",
+    "get_cluster_replication",
+    "post_cluster_replication",
+    "put_cluster_replication_id"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_controllers_controller.json

@@ -0,0 +1,26 @@
+{
+  "operationId": "delete_cluster_sdn_controllers_controller",
+  "usageNotes": "Removes an SDN controller object from the cluster SDN configuration. The controller must not be referenced by any VNet zone before deletion; remove or reassign dependent zones first. After deletion, call the SDN apply operation to push the change to all nodes.",
+  "examples": [
+    {
+      "summary": "Delete an EVPN controller named 'evpn-core'",
+      "path_params": {
+        "controller": "evpn-core"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently removes the named SDN controller configuration; any zones that depend on it will lose their controller binding and SDN connectivity will break until the configuration is applied with a valid replacement.",
+  "tips": [
+    "Returns null synchronously — there is no UPID; the change is staged and takes effect only after running the SDN apply endpoint.",
+    "Use the optional 'lock-token' param when coordinating concurrent SDN config changes to prevent conflicts.",
+    "Requires SDN.Allocate on /sdn/controllers — cluster-level privilege, not per-node."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_controllers",
+    "get_cluster_sdn_controllers_controller",
+    "create_cluster_sdn_controllers",
+    "update_cluster_sdn_controllers_controller",
+    "put_cluster_sdn"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_dns_dns.json

@@ -0,0 +1,26 @@
+{
+  "operationId": "delete_cluster_sdn_dns_dns",
+  "usageNotes": "Permanently removes an SDN DNS integration object from the cluster configuration. Requires the SDN.Allocate privilege on /sdn/dns and must be called before the deletion is propagated — run apply_cluster_sdn (POST /cluster/sdn) afterward to push the change to all nodes. If the SDN config is currently locked, obtain the lock token first and pass it via lock-token.",
+  "examples": [
+    {
+      "summary": "Delete the SDN DNS object named 'powerdns1'",
+      "path_params": {
+        "dns": "powerdns1"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently deletes the SDN DNS object and its configuration; any VNets or subnets relying on this DNS provider will lose DNS integration until a replacement object is created and applied.",
+  "tips": [
+    "The dns identifier must match the pattern [a-zA-Z][a-zA-Z0-9]*[a-zA-Z0-9] (alphanumeric, starts with a letter, minimum 2 chars).",
+    "Deletion only removes the pending config record; you must call POST /cluster/sdn to apply and propagate the change cluster-wide.",
+    "If the SDN layer is locked by another operation, the request will fail unless you supply the correct lock-token."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_dns_dns",
+    "get_cluster_sdn_dns",
+    "create_cluster_sdn_dns",
+    "update_cluster_sdn_dns_dns",
+    "apply_cluster_sdn"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_fabrics_fabric_id.json

@@ -0,0 +1,27 @@
+{
+  "operationId": "delete_cluster_sdn_fabrics_fabric_id",
+  "usageNotes": "Permanently removes an SDN fabric configuration from the cluster. Before deleting, ensure no zones, VNets, or subnets reference the fabric, as dependent objects must be removed first. This operation returns null synchronously; apply pending SDN changes afterward via the SDN apply endpoint to propagate the removal to all nodes.",
+  "examples": [
+    {
+      "summary": "Delete an SDN fabric named 'myfab1'",
+      "path_params": {
+        "id": "myfab1"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently deletes the specified SDN fabric definition from the cluster configuration; any networking policies or topology tied to this fabric must be reconfigured manually.",
+  "tips": [
+    "Fabric IDs are 2–8 alphanumeric characters (hyphens allowed in the middle); ensure the exact ID is known before issuing the delete.",
+    "Run 'get_cluster_sdn_fabrics_fabric_id' first to confirm the fabric exists and note any dependent resources.",
+    "After deletion, call the SDN apply operation to push the updated configuration to cluster nodes; skipping this leaves nodes with stale state.",
+    "Requires the SDN.Allocate privilege on /sdn/fabrics/{id}; API tokens must carry this privilege explicitly."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_fabrics_fabric_id",
+    "get_cluster_sdn_fabrics",
+    "create_cluster_sdn_fabrics",
+    "update_cluster_sdn_fabrics_fabric_id",
+    "put_cluster_sdn_fabrics"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_fabrics_node_fabric_id_node_id.json

@@ -0,0 +1,27 @@
+{
+  "operationId": "delete_cluster_sdn_fabrics_node_fabric_id_node_id",
+  "usageNotes": "Removes a specific node from an SDN fabric configuration. The caller must hold SDN.Allocate on the fabric path and Sys.Modify on the target node — both privileges are required simultaneously. This operation returns null synchronously; after deletion, apply the SDN configuration (POST /cluster/sdn) to propagate the change across the cluster.",
+  "examples": [
+    {
+      "summary": "Remove node 'pve2' from the SDN fabric 'fab01'",
+      "path_params": {
+        "fabric_id": "fab01",
+        "node_id": "pve2"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently removes the node's participation record from the SDN fabric; any fabric-specific network configuration (routes, peers, VTEP settings) tied to that node entry is lost and must be re-added manually if the node is to rejoin.",
+  "tips": [
+    "fabric_id must be 2–8 alphanumeric characters and cannot start or end with a hyphen.",
+    "Removing a node from the fabric does not remove the node from the cluster; it only detaches it from this SDN fabric's control plane.",
+    "After deletion, run POST /cluster/sdn to commit and apply the updated SDN state cluster-wide.",
+    "Verify no active SDN zones or VNets depend on this node's fabric membership before removing it."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_fabrics_node_fabric_id_node_id",
+    "post_cluster_sdn_fabrics_node_fabric_id",
+    "get_cluster_sdn_fabrics_fabric_id",
+    "put_cluster_sdn"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_ipams_ipam.json

@@ -0,0 +1,26 @@
+{
+  "operationId": "delete_cluster_sdn_ipams_ipam",
+  "usageNotes": "Permanently removes an SDN IPAM object from the cluster-wide SDN configuration. Requires the SDN.Allocate privilege on /sdn/ipams and the IPAM must not be referenced by any existing SDN zones or VNets before deletion. The API returns null synchronously; changes take effect after the SDN configuration is applied (use the SDN apply endpoint to push changes to nodes).",
+  "examples": [
+    {
+      "summary": "Delete a NetBox IPAM integration named 'netbox1'",
+      "path_params": {
+        "ipam": "netbox1"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently deletes the IPAM object configuration from the cluster; any SDN zones relying on it for IP address management will lose their IPAM association and automatic IP allocation will stop working.",
+  "tips": [
+    "Unlink the IPAM from all SDN zones before deleting — deletion of a referenced IPAM may be blocked or leave zones in a broken state.",
+    "Pass the lock-token if the SDN global config is currently locked by another operation to avoid a conflict error.",
+    "After deletion, call the SDN apply endpoint to propagate the removal to all cluster nodes."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_ipams_ipam",
+    "get_cluster_sdn_ipams",
+    "post_cluster_sdn_ipams",
+    "put_cluster_sdn_ipams_ipam",
+    "put_cluster_sdn"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_lock.json

@@ -0,0 +1,24 @@
+{
+  "operationId": "delete_cluster_sdn_lock",
+  "usageNotes": "Releases the cluster-wide SDN configuration lock, which is acquired before applying SDN changes and must be released when done or when a previous apply operation left the lock stuck. Normally supply the `lock-token` returned when the lock was acquired; use `force: true` only to break a stale lock when the original token is unavailable, as forcing bypasses the token check and can discard in-progress changes made by another session. Requires `SDN.Allocate` on `/sdn`.",
+  "examples": [
+    {
+      "summary": "Release an SDN lock using the token acquired earlier",
+      "path_params": {},
+      "params": {
+        "lock-token": "a3f8c12d-7b4e-4a91-b5f2-0e6d3c9a1b77"
+      }
+    }
+  ],
+  "destructiveReason": "Force-releasing the lock without the original token can silently discard uncommitted SDN configuration changes that another session was in the process of applying.",
+  "tips": [
+    "The lock token is returned by the corresponding lock-acquire call (POST /cluster/sdn/lock); store it immediately before making SDN changes.",
+    "Use `force: true` only as a last resort for stuck locks — confirm no other apply is actively running first.",
+    "This call returns null on success; any non-null error response means the lock was not released.",
+    "After releasing the lock, verify the SDN state with GET /cluster/sdn to confirm the expected configuration is active."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn",
+    "put_cluster_sdn"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_prefix_lists_id.json

@@ -0,0 +1,26 @@
+{
+  "operationId": "delete_cluster_sdn_prefix_lists_id",
+  "usageNotes": "Permanently deletes an SDN prefix list from the cluster configuration; requires the SDN.Allocate privilege on the specific prefix list path. Before deleting, ensure the prefix list is not referenced by any SDN zone, VNet, or firewall policy — removing a referenced list will leave dangling references that block SDN apply operations. After deletion, run the SDN apply operation (POST /cluster/sdn) to push the change to all nodes.",
+  "examples": [
+    {
+      "summary": "Delete an unused BGP prefix list named 'allowed-prefixes'",
+      "path_params": {
+        "id": "allowed-prefixes"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently removes the named prefix list and all its configured prefix entries from the cluster SDN configuration with no undo path.",
+  "tips": [
+    "Use get_cluster_sdn_prefix_lists_id first to confirm the target prefix list exists and note any references before deleting.",
+    "The optional 'lock-token' parameter is required only if the SDN configuration is currently locked by another operation — obtain it via the SDN lock endpoint.",
+    "Deletion only updates the pending SDN config; run POST /cluster/sdn to apply and propagate the change to all cluster nodes."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_prefix_lists_id",
+    "get_cluster_sdn_prefix_lists",
+    "create_cluster_sdn_prefix_lists",
+    "update_cluster_sdn_prefix_lists_id",
+    "apply_cluster_sdn"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_prefix_lists_id_entries_url_seq.json

@@ -0,0 +1,27 @@
+{
+  "operationId": "delete_cluster_sdn_prefix_lists_id_entries_url_seq",
+  "usageNotes": "Removes a single entry (identified by its sequence number) from an SDN prefix list. Requires the SDN.Allocate privilege on the specific prefix list path and changes do not take effect until the SDN configuration is applied via the apply endpoint. If the global SDN configuration is locked, supply the matching lock-token to proceed.",
+  "examples": [
+    {
+      "summary": "Delete sequence entry 10 from the 'rfc1918-private' prefix list",
+      "path_params": {
+        "id": "rfc1918-private",
+        "url_seq": "10"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently removes the specified prefix-list entry; any SDN routing policy or firewall rule relying on that prefix match will stop matching after the next SDN apply.",
+  "tips": [
+    "Run the SDN apply operation after deletion to push the change to cluster nodes — deletion alone does not activate the change.",
+    "Use the corresponding GET on /cluster/sdn/prefix-lists/{id}/entries to list sequence numbers before deleting so you target the correct entry.",
+    "The lock-token parameter is only needed when another process holds the global SDN config lock; omit it for normal single-operator workflows."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_prefix_lists_id_entries",
+    "create_cluster_sdn_prefix_lists_id_entries",
+    "get_cluster_sdn_prefix_lists_id_entries_url_seq",
+    "get_cluster_sdn_prefix_lists",
+    "apply_cluster_sdn"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_route_maps_entries_route_map_id_entry_order.json

@@ -0,0 +1,27 @@
+{
+  "operationId": "delete_cluster_sdn_route_maps_entries_route_map_id_entry_order",
+  "usageNotes": "Permanently removes a single entry (identified by its zero-based order index) from an SDN route map. The route map must exist and the caller must hold SDN.Allocate on the route-map path; after deletion, apply the SDN configuration to push the change cluster-wide. If the global SDN config is currently locked by another operation, pass the matching lock-token to avoid a conflict error.",
+  "examples": [
+    {
+      "summary": "Delete the first entry (order 0) from a route map named 'rm-transit'",
+      "path_params": {
+        "route-map-id": "rm-transit",
+        "order": 0
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently deletes the specified route map entry; any BGP policy rule that relied on this entry will stop matching after the next SDN apply.",
+  "tips": [
+    "Entry order indices are not automatically renumbered after deletion — verify remaining entries' orders before referencing them in subsequent calls.",
+    "Changes take effect cluster-wide only after calling the SDN apply endpoint; deletion alone does not update the running FRR/BGP configuration.",
+    "Retrieve the current entry list first (GET on the entries collection) to confirm the correct order index before deleting."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_route_maps_entries_route_map_id",
+    "create_cluster_sdn_route_maps_entries_route_map_id_entry",
+    "get_cluster_sdn_route_maps_entries_route_map_id_entry_order",
+    "update_cluster_sdn_route_maps_entries_route_map_id_entry_order",
+    "post_cluster_sdn_apply"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_vnets_vnet.json

@@ -0,0 +1,26 @@
+{
+  "operationId": "delete_cluster_sdn_vnets_vnet",
+  "usageNotes": "Removes an SDN VNet object from the cluster SDN configuration; the deletion is staged and does not take effect until the SDN configuration is applied via the apply endpoint. Requires 'SDN.Allocate' on the zone path that owns the VNet. The VNet must not have any active subnets or dependent objects — remove those first, or the call will be rejected.",
+  "examples": [
+    {
+      "summary": "Delete the VNet 'vnet01' from the cluster SDN configuration",
+      "path_params": {
+        "vnet": "vnet01"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently removes the VNet object configuration, which will tear down the corresponding VXLAN/VLAN overlay network and disconnect all VMs or containers mapped to that VNet once the SDN config is applied.",
+  "tips": [
+    "After deleting, call the SDN apply endpoint (PUT /cluster/sdn) to propagate the removal to all nodes.",
+    "Use the lock-token parameter if you are coordinating concurrent SDN configuration changes to avoid conflicts.",
+    "VNet identifiers are 2–8 alphanumeric characters starting with a letter — double-check the name before deleting, as the API returns null on success with no confirmation payload."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_vnets_vnet",
+    "update_cluster_sdn_vnets_vnet",
+    "get_cluster_sdn_vnets",
+    "create_cluster_sdn_vnets",
+    "apply_cluster_sdn"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_vnets_vnet_firewall_rules_pos.json

@@ -0,0 +1,29 @@
+{
+  "operationId": "delete_cluster_sdn_vnets_vnet_firewall_rules_pos",
+  "usageNotes": "Permanently removes a firewall rule at the specified position from an SDN vnet's firewall rule set. Rules below the deleted position are renumbered downward, so rely on position only within a single atomic operation. Use the `digest` parameter to guard against concurrent edits — fetch the current digest from the GET endpoint before deleting.",
+  "examples": [
+    {
+      "summary": "Delete firewall rule at position 2 for vnet 'webapp01' with a digest guard",
+      "path_params": {
+        "vnet": "webapp01",
+        "pos": 2
+      },
+      "params": {
+        "digest": "a3f1c2e9b04d78e5f6a1234567890abc"
+      }
+    }
+  ],
+  "destructiveReason": "Permanently deletes the firewall rule at the specified position; the rule cannot be recovered and remaining rules are renumbered immediately.",
+  "tips": [
+    "Omitting `pos` targets position 0 (the first rule) — always supply an explicit position to avoid accidental deletion of the wrong rule.",
+    "Rules are renumbered after deletion, so if deleting multiple rules in a loop, iterate from the highest position downward.",
+    "Requires SDN.Allocate on '/sdn/zones/<zone>/<vnet>' — confirm the calling token or user has this privilege before running.",
+    "The operation returns null on success; any HTTP error (403, 500) indicates the rule was not deleted."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_vnets_vnet_firewall_rules",
+    "get_cluster_sdn_vnets_vnet_firewall_rules_pos",
+    "put_cluster_sdn_vnets_vnet_firewall_rules_pos",
+    "post_cluster_sdn_vnets_vnet_firewall_rules"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_vnets_vnet_ips.json

@@ -0,0 +1,29 @@
+{
+  "operationId": "delete_cluster_sdn_vnets_vnet_ips",
+  "usageNotes": "Use this to remove a specific IP mapping from a VNet's DHCP/IPAM table within a given SDN zone — for example, when decommissioning a VM or reclaiming a static lease. The `zone` and `ip` parameters are both required; `mac` is optional and can be supplied to disambiguate when the same IP may appear under multiple MAC entries. The operation returns null synchronously; changes only take effect after running `apply_cluster_sdn` to push the updated SDN config to nodes.",
+  "examples": [
+    {
+      "summary": "Remove an IP mapping for a decommissioned VM in zone 'prodz' on vnet 'vnet10'",
+      "path_params": {
+        "vnet": "vnet10"
+      },
+      "params": {
+        "zone": "prodz",
+        "ip": "10.10.10.50",
+        "mac": "bc:24:11:ab:cd:ef"
+      }
+    }
+  ],
+  "destructiveReason": "Permanently removes the IP-to-MAC mapping from the VNet's IPAM table; the released IP may be immediately reassigned by DHCP, potentially causing conflicts if the original host is still active.",
+  "tips": [
+    "After deleting the IP mapping, call apply_cluster_sdn to propagate the change — without it, the mapping remains active in the running SDN until the next apply.",
+    "Omitting the `mac` parameter deletes by IP alone; if multiple MACs share the same IP (misconfiguration), verify which entry you're targeting first via get_cluster_sdn_vnets_vnet_ips.",
+    "Requires SDN.Allocate on the specific zone+vnet path — a Proxmox API token scoped to /sdn/zones/{zone}/{vnet} is sufficient."
+  ],
+  "relatedOperations": [
+    "create_cluster_sdn_vnets_vnet_ips",
+    "get_cluster_sdn_vnets_vnet_ips",
+    "apply_cluster_sdn",
+    "get_cluster_sdn_vnets_vnet"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_vnets_vnet_subnets_subnet.json

@@ -0,0 +1,28 @@
+{
+  "operationId": "delete_cluster_sdn_vnets_vnet_subnets_subnet",
+  "usageNotes": "Removes a subnet configuration object from an SDN vnet. The deletion is staged in the pending SDN config and does not take effect until the SDN configuration is applied via the apply endpoint. Requires 'SDN.Allocate' on the zone/vnet path; ensure no VMs or containers are still using the subnet's IPAM allocations before deleting.",
+  "examples": [
+    {
+      "summary": "Delete subnet 10.10.20.0/24 from vnet 'prodvn'",
+      "path_params": {
+        "vnet": "prodvn",
+        "subnet": "10.10.20.0-24"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently removes the subnet object configuration, which will eliminate associated IPAM allocations and routing rules for that CIDR once the SDN config is applied.",
+  "tips": [
+    "Changes are staged until 'apply' is called on /cluster/sdn — deletion has no live impact until then.",
+    "The subnet identifier uses the pve-sdn-subnet-id format, which typically encodes the CIDR as '<network>-<prefix>' (e.g., 10.10.20.0-24).",
+    "If the SDN config is locked by another operation, pass the lock-token obtained from the lock endpoint to proceed.",
+    "Verify no IPAM IP allocations remain on this subnet before deleting to avoid orphaned records."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_vnets_vnet_subnets_subnet",
+    "get_cluster_sdn_vnets_vnet_subnets",
+    "create_cluster_sdn_vnets_vnet_subnets",
+    "put_cluster_sdn_vnets_vnet_subnets_subnet",
+    "put_cluster_sdn"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_cluster_sdn_zones_zone.json

@@ -0,0 +1,28 @@
+{
+  "operationId": "delete_cluster_sdn_zones_zone",
+  "usageNotes": "Deletes an SDN zone configuration object from the cluster. The zone must have no VNets assigned to it before deletion — removing a zone that still has dependent VNets will fail. Requires the `SDN.Allocate` privilege on the `/sdn/zones/{zone}` path, and changes must be applied to the running SDN configuration afterward via the SDN apply endpoint.",
+  "examples": [
+    {
+      "summary": "Delete an SDN zone named 'myzone'",
+      "path_params": {
+        "zone": "myzone"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently removes the SDN zone configuration object; any network segmentation, routing policy, or VNet associations that depended on this zone must be reconfigured manually.",
+  "tips": [
+    "SDN changes are staged — after deleting the zone, call the SDN apply endpoint (PUT /cluster/sdn) to push the change to all nodes.",
+    "If the global SDN config is locked, supply the `lock-token` param to unlock and proceed in one step.",
+    "Zone identifiers are 2–8 alphanumeric characters starting with a letter; verify the exact ID with get_cluster_sdn_zones before deleting.",
+    "Check for dependent VNets first using list_cluster_sdn_vnets; deletion will be rejected if any VNet still references this zone."
+  ],
+  "relatedOperations": [
+    "get_cluster_sdn_zones_zone",
+    "list_cluster_sdn_zones",
+    "create_cluster_sdn_zones",
+    "update_cluster_sdn_zones_zone",
+    "list_cluster_sdn_vnets",
+    "put_cluster_sdn"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_nodes_node_ceph_fs_name.json

@@ -0,0 +1,29 @@
+{
+  "operationId": "delete_nodes_node_ceph_fs_name",
+  "usageNotes": "Destroys a named CephFS filesystem from the cluster node; the operation is blocked and will refuse if any enabled PVE storage entry of type 'cephfs' still references the filesystem — disable or remove those first. Pass remove-storages=true to let Proxmox clean up the pveceph-managed storage configs automatically, and remove-pools=true to also purge the underlying Ceph metadata and data pools; omitting both leaves the pools and any storage entries intact. Returns a task UPID string — poll the task endpoint to confirm completion before treating the filesystem as gone.",
+  "examples": [
+    {
+      "summary": "Destroy the CephFS named 'cephfs' on node pve1, removing both its storage entries and underlying pools",
+      "path_params": {
+        "node": "pve1",
+        "name": "cephfs"
+      },
+      "params": {
+        "remove-storages": true,
+        "remove-pools": true
+      }
+    }
+  ],
+  "destructiveReason": "Permanently destroys the CephFS filesystem and, if the optional flags are set, deletes the associated Ceph metadata and data pools along with all data stored in them.",
+  "tips": [
+    "Check for active mounts or running VMs using the filesystem before issuing this call — active clients will not be cleanly disconnected.",
+    "If remove-pools is false, the orphaned Ceph pools must be deleted manually via the pool destroy endpoint afterward.",
+    "Requires Sys.Modify at the root path ('/'); API tokens must have that privilege explicitly granted."
+  ],
+  "relatedOperations": [
+    "get_nodes_node_ceph_fs",
+    "post_nodes_node_ceph_fs_name",
+    "delete_nodes_node_ceph_pools_name",
+    "get_nodes_node_tasks"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_nodes_node_ceph_mds_name.json

@@ -0,0 +1,26 @@
+{
+  "operationId": "delete_nodes_node_ceph_mds_name",
+  "usageNotes": "Use this to permanently remove a Ceph MDS (Metadata Server) daemon from a specific node — typically after migrating the workload to another MDS or when decommissioning a node from the CephFS cluster. The target node must be online and reachable; the operation requires `Sys.Modify` at the root level. The return value is a task UPID, so poll the task status to confirm the daemon has been fully stopped and removed before proceeding with node changes.",
+  "examples": [
+    {
+      "summary": "Remove the MDS daemon named 'mds0' from node 'pve-ceph1'",
+      "path_params": {
+        "node": "pve-ceph1",
+        "name": "mds0"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently destroys the specified Ceph MDS daemon on the node, removing it from the CephFS metadata service pool; if it is the only active or standby MDS, CephFS will become unavailable until another MDS is deployed.",
+  "tips": [
+    "Verify at least one other active or standby MDS exists before destroying this one to avoid CephFS downtime.",
+    "MDS name must match the pattern `[a-zA-Z0-9]([a-zA-Z0-9-]*[a-zA-Z0-9])?` — no leading/trailing hyphens.",
+    "Use `get_nodes_node_ceph_mds` to list current MDS daemons and their states before proceeding.",
+    "Poll the returned UPID via the tasks API to confirm destruction completes before making further cluster changes."
+  ],
+  "relatedOperations": [
+    "create_nodes_node_ceph_mds_name",
+    "get_nodes_node_ceph_mds",
+    "get_nodes_node_tasks_upid_status"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_nodes_node_ceph_mgr_id.json

@@ -0,0 +1,25 @@
+{
+  "operationId": "delete_nodes_node_ceph_mgr_id",
+  "usageNotes": "Use this to permanently remove a Ceph Manager (MGR) daemon from a cluster node. The target node must be online and reachable, and the caller requires the Sys.Modify privilege at the root path. Ceph requires at least one active MGR for monitoring and orchestration — do not destroy the only running MGR unless another is already active on a different node.",
+  "examples": [
+    {
+      "summary": "Remove a Ceph MGR daemon named 'mgr0' from node 'pve1'",
+      "path_params": {
+        "node": "pve1",
+        "id": "mgr0"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently destroys the specified Ceph Manager daemon; if it is the active MGR, Ceph monitoring and dashboard services will be disrupted until a standby MGR takes over or a new one is deployed.",
+  "tips": [
+    "Run 'ceph mgr stat' or check the Ceph dashboard before destroying to confirm at least one other MGR is active or in standby.",
+    "The MGR id typically matches the hostname of the node it runs on (e.g., 'pve1'), but custom ids are possible — verify with 'ceph mgr dump' before calling.",
+    "Returns a string response (not a UPID); the operation runs synchronously from the API perspective, but Ceph cluster rebalancing may take additional time to stabilize."
+  ],
+  "relatedOperations": [
+    "post_nodes_node_ceph_mgr",
+    "get_nodes_node_ceph_mgr",
+    "get_nodes_node_ceph_status"
+  ]
+}

package/dist/catalog-pve/enrichment/delete_nodes_node_ceph_mon_monid.json

@@ -0,0 +1,27 @@
+{
+  "operationId": "delete_nodes_node_ceph_mon_monid",
+  "usageNotes": "Removes a Ceph Monitor daemon from the specified node; requires at least one other monitor in the cluster (Proxmox refuses to remove the last mon). The caller needs `Sys.Modify` at the root level. Returns a task UPID string — poll the task API to confirm completion before treating the monitor as gone.",
+  "examples": [
+    {
+      "summary": "Remove a monitor named 'pve2' from node pve2 after adding a replacement monitor elsewhere",
+      "path_params": {
+        "node": "pve2",
+        "monid": "pve2"
+      },
+      "params": {}
+    }
+  ],
+  "destructiveReason": "Permanently removes the Ceph Monitor daemon from the node, reducing quorum capacity; if only two monitors remain after removal, a single further failure will cause the cluster to lose quorum and become read-only.",
+  "tips": [
+    "Verify monitor count with GET /nodes/{node}/ceph/mon before deleting — the API blocks removal of the last mon, but dropping below three mons reduces fault tolerance.",
+    "The monid typically matches the node hostname; confirm the exact ID from the mon list endpoint before issuing the delete.",
+    "Manager daemons on the same node are unaffected — use DELETE /nodes/{node}/ceph/mgr/{id} separately if the mgr also needs removal.",
+    "The return value is a UPID string; use the tasks API (GET /nodes/{node}/tasks/{upid}/status) to poll for completion."
+  ],
+  "relatedOperations": [
+    "get_nodes_node_ceph_mon",
+    "post_nodes_node_ceph_mon",
+    "delete_nodes_node_ceph_mgr_id",
+    "get_nodes_node_tasks_upid_status"
+  ]
+}