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.

Catalog query tools give you read-only access to the MCP-Packet-Tracer built-in device and template registries without touching a live Packet Tracer session. Use them before planning a topology to verify which models are available, what ports they carry, and which of the 101 aliases the planner understands. They are also useful for double-checking that the router model you intend to use has enough ports — and for discovering which expansion module to install when it doesn’t.

pt_list_devices

Returns every device model in the catalog, along with its ports and all registered aliases.

Parameters

This tool takes no parameters.

Returns

A formatted list of all 74 device models grouped by category, each showing:
display_name
string
Human-readable model name, e.g. "Cisco 2911", "Cisco 2960-24TT", "Generic Router".
pt_type
string
The exact PT model identifier used in pt_plan_topology, pt_add_module, and the device catalog, e.g. "2911", "2960-24TT", "ISR4321".
category
string
Device category: router, switch, pc, server, laptop, cloud, accesspoint, firewall, wlc, modem, hub, bridge, repeater, and others.
ports
string
Comma-separated list of port full names with their speed, e.g. GigabitEthernet0/0, GigabitEthernet0/1, GigabitEthernet0/2 for the Cisco 2911.
The output also appends a complete alias table — all 101 registered aliases mapped to their target PT model. This is the same table that pt_plan_topology and pt_get_device_details use when resolving names like "router", "switch", or "firewall". Selected aliases include:
AliasResolves To
"router"2911
"switch"2960-24TT
"firewall"5506-X
"isr4321" / "4321"ISR4321
"isr4331" / "4331"ISR4331
"pc" / "computer"PC-PT
"server"Server-PT
"ap" / "wifi"AccessPoint-PT
"cloud" / "wan"Cloud-PT

pt_get_device_details

Returns the full port specification for a single device model, including port names and their speeds.

Parameters

model_name
string
required
Model name or alias to look up. Accepts both the exact PT type identifier (e.g. "2911", "2960-24TT") and any alias from the catalog (e.g. "router", "switch", "firewall", "isr4321"). Case-insensitive for aliases.

Returns

A JSON object:
display_name
string
Human-readable name, e.g. "Cisco 2911".
category
string
Device category, e.g. "router", "switch", "firewall".
ports
array
Array of port objects, each with name (full port name) and speed (port speed string).
total_ports
integer
Number of physical ports on the base model (before any expansion modules).

Example

Calling pt_get_device_details("2911") returns:
{
  "display_name": "Cisco 2911",
  "category": "router",
  "ports": [
    { "name": "GigabitEthernet0/0", "speed": "GigabitEthernet" },
    { "name": "GigabitEthernet0/1", "speed": "GigabitEthernet" },
    { "name": "GigabitEthernet0/2", "speed": "GigabitEthernet" }
  ],
  "total_ports": 3
}
If the model is not found, the tool returns a plain-text message and suggests calling pt_list_devices.

pt_list_templates

Returns all topology templates available in the MCP-Packet-Tracer planner. Templates define default router counts, PC counts, routing protocol, and WAN requirements that pt_plan_topology uses when template is specified.

Parameters

This tool takes no parameters.

Returns

A formatted list of all 9 topology templates, each showing:
name
string
Display name, e.g. "Multi LAN", "Three Router Triangle".
key
string
Template key to pass to pt_plan_topology as the template parameter.
description
string
Short description of the topology layout.
min_routers / max_routers / default_routers
integer
Router count constraints and defaults for this template.
default_pcs_per_lan
integer
Default PC count per LAN segment.
requires_wan
boolean
Whether the template adds a Cloud-PT WAN device by default.
default_routing
string
Default routing protocol for this template ("static", "ospf", etc.).
tags
array
Descriptive tags for discovery, e.g. ["avanzado", "redundancia", "ospf"].

Template summary

KeyNameDefault RoutersWANDefault Routing
single_lanSingle LAN1Nostatic
multi_lanMulti LAN2Nostatic
multi_lan_wanMulti LAN + WAN3Yesstatic
starStar (Hub & Spoke)1Nostatic
hub_spokeHub and Spoke4Nostatic
branch_officeBranch Office3Yesstatic
three_router_triangleThree Router Triangle3 (fixed)Noospf
router_on_a_stickRouter on a Stick1Nostatic
customCustom2Nostatic
Call pt_list_devices before planning to confirm the exact model identifier and available interfaces for the routers and switches you intend to use. If a model lacks enough ports for the planned topology, pt_get_device_details will show you what’s available, and the expansion module tools (pt_add_module, pt_install_modules_batch) can add the missing interfaces.

Build docs developers (and LLMs) love