casper-network-mcp
Related Servers
Alternatives to casper-network-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceExposes 90 production-grade tools for interacting with the complete HPE Aruba Networking Central REST API surface, including network inventory, configuration, and security management. It features enterprise-ready OAuth2 handling and semantic tool filtering for optimized performance with both hosted and local LLMs.-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to safely troubleshoot networks through read-only tools for device inventory, interface status, VLAN paths, BGP neighbors, route lookups, and interface error detection. Integrates with Microsoft Copilot Studio and Teams for natural-language-driven network diagnostics.-
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with direct access to multi-vendor network devices for tasks like configuration management, health checks, and topology discovery through 35 specialized tools. It enables natural language control over platforms including Cisco, Juniper, and Nokia using SSH, NETCONF, and SNMP protocols.12MIT
- AlicenseAqualityAmaintenanceEnables conversational automation of HPE Aruba Central network operations through Claude Code. Provides 88 tools across monitoring, configuration, and operations domains for device migration, SSID management, switch provisioning, and GreenLake Platform integration.162MIT
- AlicenseAqualityCmaintenanceLets an AI assistant inspect and adjust TP-Link Omada WiFi networks by searching, describing, and calling any of roughly 1,650 Omada Open API operations through nine tools. It is read-only by default, refusing every non-GET request unless writes are explicitly unlocked, and even then returning a dry-run preview until a change is confirmed.94MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP-capable AI agents to observe, troubleshoot, and configure Aruba CX (AOS-CX) switches through REST and SSH, with safety controls, inventory management, and verification workflows.-
TDQS
Scored across 4 tools
find_tool is clearly the discovery step, and access_check is distinct. invoke_read_tool and invoke_tool overlap because invoke_tool can also perform reads, but the descriptions clearly distinguish read-only vs. any operation, so an agent can select based on safety intent.
Three of four tools follow a verb_noun pattern (find_tool, invoke_read_tool, invoke_tool), and all use snake_case. access_check breaks the verb-first convention but remains readable and semantically clear.
Four tools is well-scoped for a gateway server that proxies many underlying network APIs. Each tool has a distinct role: discovery, read-only invocation, general invocation, and access inspection.
The surface covers discovery, read-only execution, general execution, and permission checking, which are the core operations for this meta-server. Minor gaps include no explicit list-all-tools or describe-by-name operation, though find_tool with a query likely covers these use cases.