Demo & Examples

See what the server
actually produces.

Real code examples, real output formats, and placeholders for screenshots and GIFs that show the end-to-end workflow.

Example Scenarios

Common topologies you can generate.

Simple 2-Router Lab

Two routers connected over a WAN link with one LAN each. Static routing. Great for beginners.

routers=2 pcs_per_lan=2 routing="static" dhcp=False has_wan=True
Output: 4 devices, 2 switches, 4 PCs, 6 links

OSPF Multi-Router with DHCP

Three routers running OSPF area 0 with DHCP on every LAN. A realistic branch-office topology.

routers=3 pcs_per_lan=2 routing="ospf" dhcp=True has_wan=True
Output: 3 routers, 3 switches, 6 PCs, 9+ links

Single LAN Segment

One router, one switch, multiple PCs. The simplest topology for testing IP addressing.

routers=1 pcs_per_lan=4 routing="none" dhcp=True has_wan=False
Output: 1 router, 1 switch, 4 PCs

Full Build Pipeline

The complete pt_full_build tool — plan, validate, auto-fix, generate script, configs, and explanation in one call.

routers=3 pcs_per_lan=2 routing="ospf" dhcp=True has_wan=True
Output: Plan + script + configs + explanation

Real Output

Artifacts the server generates.

These are representative outputs from the MCP server. The actual content depends on topology parameters.

PTBuilder Script (topology.js)

// Auto-generated by MCP Packet Tracer
addDevice("R1", "2911", 200, 150);
addDevice("R2", "2911", 500, 150);
addDevice("SW1", "2960-24TT", 200, 300);
addDevice("SW2", "2960-24TT", 500, 300);

addLink("R1", "GigabitEthernet0/0", "SW1",
        "GigabitEthernet0/1", "straight");
addLink("R1", "GigabitEthernet0/1", "R2",
        "GigabitEthernet0/1", "cross");

addDevice("PC1", "PC-PT", 100, 450);
addDevice("PC2", "PC-PT", 300, 450);
configurePcIp("PC1", true, "", "", "", "");
configurePcIp("PC2", true, "", "", "", "");

Router CLI Config (R1_config.txt)

enable
configure terminal
hostname R1

interface GigabitEthernet0/0
 ip address 192.168.1.1 255.255.255.0
 no shutdown
 exit

interface GigabitEthernet0/1
 ip address 10.0.0.1 255.255.255.252
 no shutdown
 exit

ip dhcp pool LAN_R1
 network 192.168.1.0 255.255.255.0
 default-router 192.168.1.1
 dns-server 8.8.8.8
 exit

router ospf 1
 network 192.168.1.0 0.0.0.255 area 0
 network 10.0.0.0 0.0.0.3 area 0
 exit

end
write memory

Plan Explanation (natural language)

Topology: 2 routers, 2 LANs, 1 WAN link

• R1 is located at (200, 150) with model 2911
  - GigabitEthernet0/0 → SW1 (LAN gateway: 192.168.1.1/24)
  - GigabitEthernet0/1 → R2 (WAN: 10.0.0.1/30)

• R2 is located at (500, 150) with model 2911
  - GigabitEthernet0/0 → SW2 (LAN gateway: 192.168.2.1/24)
  - GigabitEthernet0/1 → R1 (WAN: 10.0.0.2/30)

DHCP is enabled on both LANs.
OSPF area 0 covers all router interfaces.
Cable types: straight (router-switch), cross (router-router).

Gallery

Visual evidence of the workflow.

Add your own screenshots and GIFs here. These placeholders show where each visual fits.

topology-screenshot.png

Topology in Packet Tracer

Screenshot of a deployed 3-router OSPF topology with DHCP pools — all created by the MCP server.

live-deploy.gif

Live Deploy in Action

GIF showing devices appearing in Packet Tracer one by one as the bridge sends commands.

mcp-client.png

MCP Client Interaction

Screenshot of an AI agent using MCP tools to plan and deploy a topology step by step.

cli-config.png

CLI Config Applied

Screenshot of a router in Packet Tracer showing the applied OSPF and DHCP configuration.

To add images: Place your screenshots and GIFs in public/images/ and update the <img> sources. The placeholder structure is ready — just replace the placeholder divs with <img src="/images/your-file.png">.

Try it yourself

Run this in 60 seconds.

Clone, install, start, and connect your MCP client. Then ask it to build a topology.

Clone the Repo 
git clone https://github.com/Mats2208/MCP-Packet-Tracer.git
cd MCP-Packet-Tracer
pip install -e .
python -m src.packet_tracer_mcp

# Then in your MCP client:
> "Build a 3-router lab with OSPF and DHCP"