Skip to main content
Glama
Arminfx7

GNS3 NetForge MCP

by Arminfx7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to GNS3 NetForge MCP

No user-submitted related servers found.

    Related Servers

    • GNS3 Network Simulator MCP

      Wael-Rd
      A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      42
      25
      MIT

    • gns3-mcp

      Olaw2jr
      A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to control GNS3 network emulation labs. Supports building topologies, managing devices, capturing packets, and automating device CLIs.
      100
      MIT

    • EVE-NG MCP Server

      moimran
      F
      license
      A
      quality
      D
      maintenance
      A 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.
      26
      15
      -

    • PNETLab MCP Server

      omichelbraga
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      31
      4
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools map to distinct resources (project, node, link, drawing, project_docs) or distinct access methods (ssh, console, http_client), and the ssh/console split is explicitly explained. The main overlap is query_resource, a 'universal' tool whose read purpose duplicates the list actions of project/node/link/drawing, which could cause misselection.

    Naming Consistency4/5

    All names use snake_case, and the CRUD-style tools consistently use bare resource nouns (project, node, link, drawing, tftp). A few deviation tools use verb phrases (query_resource, export_topology_diagram, search_tools), but the convention remains readable and predictable.

    Tool Count5/5

    15 tools is well-scoped for a full GNS3 lab-management server, and each tool covers a meaningful, non-redundant slice (topology CRUD, device access, file transfer, docs, discovery). Nothing feels padded or missing at the count level.

    Completeness4/5

    The surface is broad: project/node/link/drawing CRUD, console+SSH device access, file and TFTP management, docs, notifications, topology export, and tool discovery. Minor gaps exist — no snapshot management (only referenced via events), no template CRUD, and no project delete — but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources