MCP-Telecom
Related Servers
Alternatives to MCP-Telecom
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides read-only SSH access to network devices (routers, switches, firewalls) with command allow/deny policies, nt-templates output parsing, and an audit trail, enabling an AI agent to query device state securely.10MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to execute SSH commands on network devices using natural language, supporting multiple vendors and authentication methods for automated network management.-
- 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.11MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Cisco IOS-XE network devices over SSH using structured tools. Provides read and write capabilities for network management with built-in validation and security.-
- AlicenseNot gradedqualityCmaintenanceEnables AI-assisted management of multi-vendor network devices (Cisco, Juniper, Nokia, Arista, Linux) through natural language, supporting health checks, configuration changes, routing analysis, and automation workflows.MIT
- 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.-
TDQS
Scored across 58 tools
Each tool targets a specific network operation or data type (e.g., show_interfaces vs show_interface_detail, show_bgp_summary vs show_bgp_neighbors). Parallel variants are clearly distinguished from single-device tools. The only potential overlap (run_command vs run_vendor_operation) is resolved by descriptions. All tools have distinct purposes.
Nearly all tools follow a consistent verb_noun pattern (backup_config, compare_configs, health_check, show_interfaces, telemetry_subscribe, etc.). The clab_ prefix group is consistent within itself, and the overall naming is predictable and easy to navigate.
With 58 tools, the server is quite large. While each tool serves a specific purpose in network management, the count feels excessive for a single MCP server. Many show_* tools (20+) and parallel variants add to the number. A more streamlined set could reduce cognitive load without losing functionality.
The tool surface covers a comprehensive range of network operations: configuration backup/comparison, health checks, detailed show commands, SNMP, NETCONF, telemetry, topology discovery, compliance, and parallel execution. The only notable gap is the lack of configuration write operations, but that aligns with the server's read-only focus. Overall, the domain is well-covered.