F
licenseA
qualityF
maintenanceAn MCP server that integrates Nornir with NAPALM and Netmiko, enabling LLMs to orchestrate multi-vendor network infrastructure through natural language.
5
2
-
Itential MCP Server
Officialby itential
Related Servers
Alternatives to Itential MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP server that allows LLMs to create, configure, validate, and explain Cisco Packet Tracer network topologies. It provides a comprehensive suite of tools for generating deployment scripts, CLI configurations, and automated network troubleshooting.187 PyPI178MIT
- AlicenseAqualityBmaintenanceAn MCP server that enables LLMs to retrieve structured network information, including routing, interfaces, MPLS, and topology, from devices using gNMI and OpenConfig models. It facilitates real-time network analysis, log filtering, and status monitoring through a standardized interface.1014BSD 3-Clause
- AlicenseNot gradedqualityDmaintenanceMCP server for network operations that lets AI assistants interact with Cisco/Juniper network devices through safe, well-defined tools like compliance audits and configuration backups.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes Cisco IOS-XE devices as tools for LLM clients, enabling safe configuration changes with revert timer and connectivity verification.Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that exposes live network monitoring data as Resources and diagnostic capabilities as Tools, letting AI assistants query network health conversationally.6MIT
TDQS
B3.2/5.0
Scored across 76 tools
Disambiguation2/5
Several tools have unclear boundaries. get_gateways and get_services have identical descriptions, and start_workflow is explicitly a wrapper around trigger_automation, causing redundancy. Multiple run_* tools (run_service, run_action, run_command, run_command_template) also have overlapping semantics that could lead to misselection.
Naming Consistency3/5
Most tools use a verb_noun pattern (get_, create_, run_), but conventions are mixed: detail retrievals sometimes use describe_ and sometimes get_ (e.g., get_device_configuration vs describe_inventory). Execution verbs are inconsistent (run_, start_, trigger_), and some names are verbose and asymmetric (describe_session_token_usage vs get_agent_session_token_usage).
Tool Count1/5
With 76 tools, the server is extremely over-scoped. This far exceeds typical MCP servers and even the broad platform it targets, overwhelming agents and increasing the chance of selecting the wrong tool. The count is not well-calibrated for usability.
Completeness3/5
The tool set covers a wide range of platform capabilities, but many entity types lack lifecycle operations. For example, device groups, command templates, golden config trees, templates, and resources all have create/read/run but no update or delete, leaving notable gaps in management workflows.
Maintenance
ActivityNo data
ResponsivenessUnresponsive