A
licenseC
qualityC
maintenanceEnables AI agents to control GNS3 network emulation labs. Supports building topologies, managing devices, capturing packets, and automating device CLIs.
100
MIT
GNS3 MCP Server
by ChistokhinSV
Related Servers
Alternatives to GNS3 MCP Server
No user-submitted related servers found.
Related Servers
- 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.4225MIT
- 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.MIT
- AlicenseAqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityDmaintenanceEnables natural language control of ESP8266 and Raspberry Pi IoT devices via Claude Desktop using the MCP protocol.MIT
TDQS
A3.9/5.0
Scored across 15 tools
Disambiguation5/5
Each tool has a clearly defined purpose: ssh and console are differentiated by use case (SSH preferred, console for initial setup), and all other tools cover distinct domains (project, node, link, drawing, file management, etc.). No two tools overlap in function.
Naming Consistency4/5
Tool names generally use lowercase words with underscores for compound names (e.g., gns3_connection, project_docs, query_resource), which is consistent. However, there is no strict verb_noun pattern; many tools are single nouns (ssh, node, console, drawing). This is acceptable but not perfectly uniform.
Tool Count5/5
With 15 tools, the set is well-scoped for managing GNS3 network simulation labs. It covers project, node, link, drawing, device access (SSH/console), TFTP, HTTP client, documentation, and tool discovery without being overwhelming or too sparse.
Completeness4/5
The tool set covers most core workflows: CRUD for projects, nodes, links, drawings; device access via console and SSH; file operations on Docker nodes; documentation; topology export; and auxiliary services (TFTP, HTTP). Minor gaps like template management or snapshot operations are missing but not critical for typical lab operations.
Maintenance
ActivityInactive
ResponsivenessUnresponsive