palo-alto-bgp-ipsec
Related Servers
Alternatives to palo-alto-bgp-ipsec
No user-submitted related servers found.
Related Servers
- FlicenseBqualityNot gradedmaintenanceEnables management of Palo Alto firewalls through their REST API, including system information retrieval, PAN-OS upgrades, HA firewall management via Panorama, content updates, and certificate management.6-
- FlicenseNot gradedqualityFmaintenanceEnables MCP clients to interact with Palo Alto Networks firewalls and Panorama, providing tools to retrieve address objects, security zones, policies, and system information.14-
- FlicenseCqualityDmaintenanceEnables comprehensive management of Palo Alto Networks firewalls through a modular suite of servers for security policies, network objects, device operations, and system configuration.4-
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Palo Alto Networks firewalls via XML API for configuration and monitoring tasks.-
- AlicenseNot gradedqualityCmaintenanceEnables safe interaction with Juniper Junos devices (SRX firewalls) via MCP, providing operational read tools and a configuration change flow with device-side diff preview and automated rollback.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Palo Alto Networks APIs through a Model Context Protocol server. Generated using Postman MCP Generator, it provides automated tools for managing Palo Alto services through natural language commands.-
TDQS
Scored across 63 tools
Most tools target distinct resources or lifecycle phases, and descriptions are detailed, but several pairs overlap conceptually: validate_ipsec_candidate and _v2, plan_status vs operation_status, and generic set_config/delete_config vs typed resource tools. An agent could misselect without careful reading.
There are two broad conventions: panorama_* lifecycle tools and generic get_/delete_/commit-style tools. Within each group naming is mostly consistent, but mixing remove vs delete, list vs get, commit vs panorama_commit, and _v2 suffixes makes the overall pattern inconsistent.
63 tools is far beyond the 50+ threshold for an extreme count mismatch. Many could be consolidated, especially the status/list/operation metadata helpers, log variants, and duplicate validation versions.
The core IPsec+BGP-over-Panorama lifecycle is well covered: preflight, suggest, plan_ipsec, apply, validate, plan_bgp, apply_bgp, validate, runtime verify, remove, commit, and push. Minor gaps exist for object updates and the duplicate v1/v2 validation path, but generic set_config and delete/add provide workarounds.