hpe-security-director-cloud-mcp
Related Servers
Alternatives to hpe-security-director-cloud-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProduction-grade MCP server that exposes the complete HPE Aruba Networking Central REST API as 90 tools across 19 categories, enabling AI assistants to manage Aruba Central networks.-
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes HPE Aruba EdgeConnect Orchestrator SD-WAN infrastructure as LLM-callable tools for listing appliances, reading interface/tunnel/bandwidth state, and changing HPE SSE tunnel state.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceProvides 129 MCP tools for querying and managing Hillstone StoneOS firewalls, enabling AI assistants to perform network operations through natural language.-
- FlicenseNot gradedqualityBmaintenanceExposes Juniper Mist REST API as 22 curated MCP tools, enabling AI agents to query and manage network resources like sites, devices, WLANs, and Marvis AI insights through natural language.-
- FlicenseBqualityCmaintenanceA Model Context Protocol server for managing Palo Alto Networks Strata Cloud Manager firewall configurations through natural language in Claude. It provides 149 tools covering the full configuration lifecycle including policy objects, security rules, NAT, and profiles with multi-tenant support.100-
- AlicenseAqualityDmaintenanceA community MCP server for Cisco Secure Access that exposes the Secure Access REST API to AI clients as a curated catalog of tools for Admin, Deployments, Investigate, Policies, and Reports.421Apache 2.0
TDQS
Scored across 368 tools
Most tools follow a clear resource+action pattern, and descriptions generally resolve ambiguity between similar objects. However, at 368 tools there are many close parallels—firewall vs. NAT policy hierarchies, ungrouped rules vs. rules-in-group, and multiple filtering profile families—that create real selection friction for an agent.
The sdcloud_<verb>_<object> convention is used broadly and is mostly predictable. Minor deviations like tunnel_status_count, remove_devices vs. delete_*, change_password, set_* vs. update_*, and start_*_job vs. deploy/preview prevent a perfect score.
368 tools is an extreme count for any MCP server, even one covering a broad security management domain. The surface is far too large for an agent to reliably navigate, with dozens of near-parallel CRUD, hierarchy, and job-polling tool families.
The toolset covers an unusually wide range of domains: firewall/NAT policies, security profiles, devices, templates, certificates, and users. A few partial areas remain—subscription associations lack a delete operation, device image definitions lack get/update, and the external probe has create/get/delete but no update—but there are no severe dead ends.