GNS3 MCP Server
Related Servers
Alternatives to GNS3 MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables automating GNS3 network labs via the Model Context Protocol, including managing projects, nodes, links, virtual machines, and console commands from ChatGPT.152MIT
- AlicenseCqualityCmaintenanceEnables AI agents to control GNS3 network emulation labs. Supports building topologies, managing devices, capturing packets, and automating device CLIs.1002MIT
- AlicenseBqualityDmaintenanceEnables AI-powered network engineering by providing natural language control over GNS3 network simulations. Supports creating projects, building network topologies, managing devices, controlling simulations, and analyzing network traffic through conversational AI interactions.4228MIT
- 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 gradedqualityDmaintenanceConnects Claude with Cisco Packet Tracer 9.x to control network topologies, configure devices with IOS commands, and run diagnostics via natural language.1MIT
- AlicenseAqualityDmaintenanceEnables AI clients like Claude Desktop and Cursor to control Cisco Packet Tracer through natural language, including generating network topologies, running device configurations, and managing simulations.23MIT
TDQS
Scored across 15 tools
Most tools map cleanly to a single resource (project, node, link, drawing, tftp, project_docs) with distinct action sets. The main overlap is ssh vs console (both device access, though the console description explicitly says to prefer SSH) and query_resource, a catch-all that can read the same data as the list actions of node/link/project. These boundaries are documented well enough that an agent can pick correctly, but they are not perfectly disjoint.
The dominant pattern is consolidated noun tools with an 'action' parameter (node, project, link, drawing, tftp, ssh, console, notification), which is coherent. However, several tools break that pattern with verb_noun names (export_topology_diagram, query_resource, search_tools) and others use compound noun names (gns3_connection, node_file, project_docs, http_client). It is readable but mixes two conventions rather than following one predictable scheme.
Fifteen tools for a lab-automation server covering projects, topology, device access, files, and discovery is well within a reasonable range. The v0.47.0 batch/CRUD consolidation (e.g. separate ssh_configure/ssh_command folded into ssh, create/delete/set folded into node) keeps the surface lean rather than sprawling.
The surface covers the full lab lifecycle: project CRUD, node CRUD plus state control, link connect/disconnect, drawings, docs, file I/O, TFTP, notifications, connection recovery, topology export, and a universal resource query backstop. Notable gaps are snapshots (referenced only as an event type) and template management — node create takes a template_name but there is no action to list or inspect templates — which an agent must work around.