GNS3 MCP Server
Let AI agents build, wire, configure and troubleshoot your GNS3 network labs.
An MCP server for GNS3 3.x. Your agent gets tools to:
- open and create projects, add nodes from templates, set RAM, CPUs, disks and adapters
- cable nodes together and start, stop or restart them, one by one or by pattern
- type into device consoles and run commands over SSH (Netmiko, 200+ device types)
- read the topology, the project notes and live GNS3 events; draw and export diagrams
You need a GNS3 3.x server (the GNS3 VM or gns3server) and uv.
Install
Let your agent do it
Paste this into Claude Code, Codex, Cursor or any other agent that can run commands:
It follows the steps for agents below, asks you for the GNS3 server details, and runs the setup. You can type the password into your own terminal instead of giving it to the agent.
Or install it yourself
-
Install uv if
uvx --versiondoes not work, then open a new terminal.Windowspowershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"macOS / Linuxcurl -LsSf https://astral.sh/uv/install.sh | sh -
Connect your agent. Run this with your agent's name from the table below. It asks for the GNS3 host, port, user and password, checks the login, and sets the agent up:
uvx gns3-mcp configure claudeName Agent claudeClaude Code claude-desktopClaude Desktop cursorCursor vscodeGitHub Copilot in VS Code windsurfWindsurf (Devin Desktop) clineCline kiroKiro opencodeOpenCode codexOpenAI Codex geminiGemini CLI Agent not listed, or you prefer to edit the config yourself? This prints the ready-made config and instructions for every agent, with the file paths for your computer:
uvx gns3-mcp configure --instructions - Restart the agent and ask it: "List my GNS3 projects".
What it changes
~/.gns3-mcp/.envkeeps the GNS3 settings. Agent configs hold no passwords.- The agent's MCP config gets one entry,
gns3. Your other servers stay, and a backup of the file is kept. - The agent's rules file gets a short marked block that tells it to use the GNS3 tools. Skip it with
--no-instructions.
Useful options: --project writes the config into the current folder instead of the user-wide one, and --dry-run shows the changes first.
Other ways
- Claude plugin for Claude Code and Cowork, which adds a lab skill too. One command in a terminal adds it for the terminal and the desktop app:
claude plugin install gns3-lab --marketplace ChistokhinSV/gns3-mcp. In Cowork: Customize > Plugins > Add > Add marketplace, enterChistokhinSV/gns3-mcp. - Claude Desktop extension: download
mcp-server.mcpbfrom the latest release and double-click it. - Shared HTTP server: Docker image or Windows service; see the README.
Instructions for AI agents
If you are an AI agent installing this server for the user, follow install.md. In short:
- Pick your name from the table above, or ask the user. If you are not listed, run
uvx gns3-mcp configure --instructionsand follow the guide it prints. - Check
uvx --version. If uv is missing, ask the user before installing it. - Ask the user for the GNS3 host, the port (80 on the GNS3 VM, 3080 for gns3server) and the username.
- Ask the user to run
uvx gns3-mcp configure <name>in their own terminal, which keeps the password out of the chat. If they ask you to run it, pass the password only in theGNS3_PASSWORDenvironment variable, add--host --port --user --yes, and never repeat the password. - Check that the output says
login check: OK, then tell the user to restart the agent.