Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Mats2208/MCP-Packet-Tracer/llms.txt

Use this file to discover all available pages before exploring further.

MCP Packet Tracer exposes 33 MCP tools that give any LLM full programmatic control over Cisco Packet Tracer. Together they cover the complete network engineering workflow: translating a natural-language description into a validated TopologyPlan, generating PTBuilder JavaScript and IOS CLI configs, deploying the topology live into a running Packet Tracer instance, and then managing that topology interactively — querying, renaming, moving devices, installing expansion modules, and applying ACL and NAT policies. Every tool is callable from any MCP client (GitHub Copilot, Claude, Codex, Cursor) without leaving the editor.

Tool Groups

GroupToolsWhat They Do
Catalog3List supported devices, templates, and per-model port details
Estimation1Dry-run count of devices, links, and configs before planning
Planning1Generate a complete TopologyPlan JSON from parameters
Validation & Fixing3Validate plans against 34 error codes, auto-fix common issues, explain decisions
Generation2Generate PTBuilder JS scripts and IOS CLI config blocks
Full Pipeline1Single-call plan + validate + generate + explain + estimate
Deploy3Copy script to clipboard, live-deploy to PT via bridge, check bridge status
Topology Interaction6Query, delete, rename, move devices; delete links; send raw JS
Export & Projects3Export files to disk, list and load saved projects
Modules3List, add, and batch-install expansion modules (HWIC, NIM, NM)
ACL2Apply and remove Access Control Lists on live routers
NAT / PAT2Apply and remove Static NAT, Dynamic NAT, or PAT on live routers

All 33 Tools

ToolDescription
pt_list_devicesLists all 74 supported device models with their ports and categories
pt_list_templatesLists all available topology templates with descriptions and defaults
pt_get_device_detailsReturns full port and interface details for a specific device model
pt_estimate_planDry-run estimation — counts devices, links, and configs without generating the full plan
pt_plan_topologyGenerates a complete TopologyPlan — devices, links, IPs, DHCP, routes, and modules
pt_validate_planValidates a TopologyPlan against 34 typed error codes, returning errors and warnings
pt_fix_planAuto-corrects common plan errors: wrong cables, missing ports, and router model upgrades
pt_explain_planReturns a natural-language explanation of every decision in the plan
pt_generate_scriptGenerates the PTBuilder JavaScript script (addDevice, addModule, addLink)
pt_generate_configsGenerates per-device IOS CLI configuration blocks for routers, switches, and hosts
pt_full_buildAll-in-one pipeline: plan → validate → generate → explain → estimate in a single call
pt_deployCopies the topology script to the Windows clipboard with step-by-step paste instructions
pt_live_deploySends commands directly to a running Packet Tracer instance via the HTTP bridge
pt_bridge_statusChecks whether the HTTP bridge is active and PTBuilder is connected
pt_query_topologyReads the currently loaded devices from the active Packet Tracer topology
pt_delete_deviceRemoves a device and all its links from the active topology in Packet Tracer
pt_rename_deviceRenames a device in the active Packet Tracer topology
pt_move_deviceMoves a device to new canvas coordinates in the Packet Tracer logical view
pt_delete_linkRemoves the link connected to a specific interface on a device
pt_set_portConfigures low-level port attributes (bandwidth, duplex, description, MAC) on a live device
pt_send_rawSends arbitrary JavaScript to the Packet Tracer Script Engine via the bridge
pt_exportExports the plan, PTBuilder JS script, and IOS CLI configs to files on disk
pt_list_projectsLists all previously saved topology projects
pt_load_projectLoads a previously saved project by name
pt_list_modulesLists expansion modules from the catalog, optionally filtered by router model or category
pt_add_moduleInstalls a single expansion module in a slot on an existing device in Packet Tracer
pt_install_modules_batchInstalls multiple modules across one or more devices in a single power-cycle operation
pt_apply_aclApplies a standard, extended, or named ACL to a router interface via IOS CLI
pt_apply_acl_objectApplies an ACL using the PT AclProcess object API instead of CLI
pt_remove_aclRemoves an ACL and its interface binding from a router via IOS CLI
pt_remove_acl_objectRemoves an ACL using the PT AclProcess object API
pt_apply_natApplies Static NAT, Dynamic NAT, or PAT (overload) to a router
pt_remove_natRemoves NAT translation rules, pool, and ACL from a router

Workflow

The tools are designed to work together as a pipeline. A natural-language request flows through planning, validation, generation, and finally deployment into a live Packet Tracer instance.
Natural language prompt
  ↓ pt_plan_topology / pt_full_build
TopologyPlan (JSON)
  ↓ pt_validate_plan → pt_fix_plan
Validated Plan
  ↓ pt_generate_script / pt_generate_configs
PTBuilder JS + IOS CLI
  ↓ pt_live_deploy
Running Packet Tracer Topology
pt_full_build vs. the step-by-step pipelinept_full_build runs the entire pipeline in a single call and returns a human-readable report — ideal when you want a quick, complete build without intermediate steps. Use the individual tools (pt_plan_topologypt_validate_planpt_fix_planpt_generate_script) when you need to inspect or modify the plan at each stage, or when you need machine-readable JSON to pass to downstream tools like pt_live_deploy or pt_generate_configs. The output of pt_full_build is a formatted report, not direct JSON input for other tools.

Tool Group Pages

pt_plan_topology

Generate a complete TopologyPlan from a natural-language description

pt_validate_plan

Validate a TopologyPlan against 34 typed error codes

pt_fix_plan

Auto-fix cables, ports, and router model mismatches

pt_explain_plan

Get a human-readable summary of every plan decision

pt_estimate_plan

Dry-run device, link, and config count estimation

pt_full_build

All-in-one plan → validate → generate → deploy pipeline

Build docs developers (and LLMs) love