Skip to main content
Glama
Sign In
Packet Tracer MCP

Packet Tracer MCP

by YanamiAnnaForensic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Packet Tracer MCP

No user-submitted related servers found.

    Related Servers

    • pktctl

      TantiE100
      A
      license
      B
      quality
      A
      maintenance
      Drives a running Cisco Packet Tracer over its native IPC protocol (PTMP): build and cable topologies, configure IOS, test with ping and simulation mode, and reach the whole IPC API through 72 tools.
      72
      3
      MIT

    • Tracerlab

      atharv-santosh
      A
      license
      B
      quality
      A
      maintenance
      Enables MCP clients to build and troubleshoot Cisco Packet Tracer networks by adding devices, cabling them, pushing IOS configurations, addressing interfaces, configuring routing, running pings, and reading/writing .pkt files without Packet Tracer open.
      42
      MIT

    • ptmcp

      zoujiapeng
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive Cisco Packet Tracer 8.x in the background, building topologies, auto-selecting cables so links come up green, running device CLI commands, reading back configuration, and exporting .pkt files without dialogs or stealing window focus.
      MIT

    • ptlab

      samu-jpg
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to design Cisco Packet Tracer labs from a device/link spec — cables, IPs, VLANs, routing and DHCP — and generate ready-configured .pkt files, .pka activities and SVG previews without opening Packet Tracer. It also exposes primitives to add, edit and inspect devices, services, ACLs and NAT in existing lab files.
      GPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: topology export, IPC status, device listing, network lifecycle, device creation/connection, PC IPv4, IOS configuration, show output, ipconfig, ping, and time advancement. The only near-overlap is pt_ping versus pt_fast_forward, but their purposes are clearly separated by the descriptions.

    Naming Consistency4/5

    All tools use a consistent pt_ prefix and snake_case, making the namespace predictable. There is minor variation between verb-led names (list_devices, create_device, configure_ios) and noun/state names (status, topology_png, pc_ipconfig), but the pattern remains readable.

    Tool Count5/5

    Fourteen tools is well-scoped for a Packet Tracer automation server, covering connection, topology, device, configuration, and simulation operations without excessive fragmentation. Each tool appears to earn its place.

    Completeness3/5

    The surface covers network creation/open/save, device creation, connecting devices, configuration, and verification. However, there is no tool to delete devices or disconnect links, and no tool to list available ports/interfaces, which is a notable gap because pt_connect_devices requires knowing free ports.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources