mcp-eveng
Related Servers
Alternatives to mcp-eveng
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP 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
- 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.1425 PyPI2Apache 2.0
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables LLMs to manage network topologies, labs, nodes, and configurations in the EVE-NG network emulation platform through a standardized interface.2615-
- AlicenseNot gradedqualityDmaintenanceAn MCP server for managing home lab VMs and PNETLab topologies, enabling AI agents to power VMs, handle snapshots, and verify device configurations with explicit allowlists and confirmation gating.MIT
- FlicenseAqualityDmaintenanceMCP server for Cisco Modeling Labs (CML) that enables building, managing, and running network labs through MCP tools, wrapping the CML Python SDK for lab/topology CRUD, node/link management, and configuration.22-
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with NetBox API, enabling users to query and manage NetBox resources such as devices through natural language.MIT
TDQS
Scored across 36 tools
Most tools have clearly distinct purposes, with operations well-organized around labs, nodes, networks, and folders. A few tools like `edit_lab_node` and `edit_lab_nodes_by_template` have overlapping scope but are differentiated by bulk vs. single-node editing.
Tool names follow a consistent verb_noun pattern (e.g., `add_lab_node`, `delete_lab_network`, `start_node`). Minor inconsistencies exist like `change_node_delay` vs. `edit_lab_node`, but overall the pattern is predictable and readable.
With 36 tools, the surface is large but well-justified by the complexity of EVE-NG lab management (folders, labs, nodes, networks, wiring, lifecycle). Each tool covers a distinct operation, and the count feels appropriate for the domain.
The tool set covers the full lifecycle for EVE-NG: CRUD for folders, labs, nodes, and networks; node wiring; power operations; export; and status. No obvious gaps for common lab management tasks, including advanced features like bulk editing and sharing.