gns3-mcp
Related Servers
Alternatives to gns3-mcp
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.4228MIT
- AlicenseAqualityCmaintenanceEnables automating GNS3 network labs via the Model Context Protocol, including managing projects, nodes, links, virtual machines, and console commands from ChatGPT.152MIT
- AlicenseAqualityBmaintenanceEnables control of GNS3 network lab automation, including projects, nodes, consoles, and SSH, through Claude Desktop or any MCP-compatible client.151,224 PyPI17MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to plan and validate Cisco network topologies, generate IOS CLI configurations, deploy devices and cabling live in Cisco Packet Tracer, and run connectivity diagnostics such as ping and packet capture.3MIT
- AlicenseAqualityDmaintenanceEnables programmatic control of a PNETLab network-emulation lab via natural language, allowing users to build topologies, wire links, push device configs, and boot the lab through an LLM agent.316Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to plan, create, and control Cisco Packet Tracer network topologies in real time, including deploying devices and cabling, configuring IPs and IOS CLI, and querying or clearing topologies through an HTTP bridge.MIT
TDQS
Scored across 122 tools
Each tool has a clearly distinct purpose, organized by resource type (acl, appliance, node, project, etc.) with descriptive names. Even within high-volume groups like node tools, actions such as start, stop, suspend, reload, isolate are unambiguous.
Tool names consistently follow a prefix_resource_action pattern in snake_case (e.g., acl_create, node_start, project_delete). The only outlier is 'whoami', but it's a single exception.
With 122 tools, the count far exceeds typical well-scoped ranges (3-15). While GNS3 is complex, this volume is overwhelming and likely to cause navigation issues for agents.
The tool set covers the full lifecycle of GNS3 operations: projects, nodes, templates, links, captures, images, appliances, users, ACLs, roles, pools, snapshots, and console interaction. No obvious gaps for basic simulation workflows.