A
licenseA
qualityC
maintenanceThin MCP server for Cisco CML2 that exposes the live OpenAPI specification and a generic API call tool, enabling models to interact with CML2 by reading the spec first.
2
MIT
cml-mcp-server
by jonathanLynn
Related Servers
Alternatives to cml-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for controlling EVE-NG network emulator instances via REST API, enabling lab/node/network management, topology editing, and device operations through natural language.36MIT
- AlicenseBqualityDmaintenanceAn MCP server that gives Claude and other LLM agents programmatic access to EVE-NG network labs, enabling creation, configuration, and management of virtual network topologies through natural language.142Apache 2.0
- 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.164MIT
- FlicenseNot gradedqualityDmaintenanceA comprehensive toolkit that enables automated interaction with Cisco Modeling Labs (CML) for creating network topologies, configuring devices, and managing lab environments.1-
- AlicenseAqualityBmaintenanceMCP server for controlling PNETLab v6 network labs via natural language, enabling topology creation, node management, config push, console interaction, and link fault injection.241Apache 2.0
TDQS
A3.5/5.0
Scored across 22 tools
Disambiguation5/5
Each tool targets a distinct resource and action, from lab-level operations (create_lab, start_lab) to node-level (add_node, stop_node) and link-level (add_link, remove_link). Aggregates like build_topology and example-specific tools are clearly separated, and even similar-looking config tools (get_node_config vs extract_node_config) are explicitly differentiated.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (e.g., list_labs, create_lab, add_node, delete_lab). Verbs and nouns are predictable, and related actions use clear prefixes like start_/stop_, add_/remove_, and get_/list_.
Tool Count3/5
With 22 tools, the server sits in the heavy range (16-25) according to the calibration rubric. While each tool serves a clear purpose, the sheer number might be overwhelming for an agent, and some operations (e.g., example topology deployment) could have been consolidated without losing clarity.
Completeness4/5
The tool surface covers core lab lifecycle (create, delete, start, stop, wipe), node management (add, remove, config, console), and link management (add, remove). However, there is no direct update for lab metadata or node resources (RAM, image), and no way to edit a link without recreating it, which are minor gaps agents can work around.
Maintenance
ActivitySlowing
ResponsivenessNo issues