packet-tracer-mcp

Purpose: Automating Cisco Packet Tracer topology planning, validation, correction, generation, and configuration.

Inferred · not functionally tested

Audience: networking students, CCNA learners, and network automation developers

Inferred · not functionally tested

Functions: agents, workflow_automation

Inferred · not functionally tested

Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org. These links do not verify the individual claims.

packet-tracer-mcp is a Frameworks & runtimes project. Inferred · not functionally tested: It focuses on automating Cisco Packet Tracer topology planning, validation, correction, generation, and configuration. Inferred · not functionally tested: packet-tracer-mcp is an open-source project aimed at networking students, CCNA learners, and network automation developers. Basis unknown · not verified: packet-tracer-mcp is open source under the MIT license. Basis unknown · not verified: It ships for the command line, and it can be self-hosted.

Behind packet-tracer-mcp is Mats2208, and it first shipped in 2026. Development happens publicly on GitHub with 152 stars and 82 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are topology planning, topology validation, and automatic fixes. Basis unknown · not verified: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.