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
The four tools have largely distinct roles: discovery (find_tool), authentication/status (access_check), safe execution (invoke_read_tool), and full execution (invoke_tool). The read/write split between the two invoke tools is clear and enforced, though agents must first discover a tool's kind before choosing the right invoker.
Three tools follow a verb_noun pattern (find_tool, invoke_tool, invoke_read_tool), while access_check uses noun_verb ordering. This is a minor deviation and all names remain readable and semantically clear.
Four meta-tools are exactly right for a gateway that fronts a large external API surface via discovery rather than exposing every endpoint directly. Each tool has a distinct, necessary role.
The surface covers discovery with schema lookup, authentication inspection, read-only execution, and mutating execution, with pagination and field filtering handled in the read path. A direct way to list all available tool kinds without a query is absent but workable through find_tool.