Tracerlab

io.github.atharv-santoshPublished by GitHub account atharv-santoshv0.1.6Updated Oct 29, 2026

Build and verify Cisco Packet Tracer networks from an AI agent.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

MCP server that lets an AI agent build, configure and troubleshoot Cisco Packet Tracer 9 networks, including devices, cabling, IOS configs and routing.

What you can do
  • Add devices and cable them together in a running Packet Tracer
  • Push IOS configurations, assign addressing and set up routing protocols
  • Run pings and diagnose what is broken in a network
  • Read and write .pkt files without Packet Tracer open
  • Build ready-made labs in one call (router on a stick, OSPF/EIGRP/RIP, NAT, HSRP, EtherChannel, IPv6)
  • Inspect running configurations on devices
When to use it
Useful for network engineers, students and instructors who want an assistant to assemble or debug Cisco Packet Tracer topologies from a prompt instead of clicking through the GUI, or to inspect and edit .pkt files directly.
Requirements
Runs locally over stdio via uvx from the tracerlab PyPI package. Needs uv and Cisco Packet Tracer 9 installed; a one-time Packet Tracer extension install and restart are required, and the PT-MCP Bridge window must be running. No API keys or environment variables are declared.
Before you install
The server changes the network you are working on: it adds devices, cables, pushes IOS configs and writes .pkt files, so work on copies of important labs. It requires installing a script module into Packet Tracer, which runs inside that application.

Installation

In SourceWeft

  1. Open Tracerlab in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Tracerlab

MCP server for Cisco Packet Tracer 9. Lets Claude Code (or any MCP client) build networks in a running Packet Tracer: add devices, cable them, push IOS configs, address everything, set up routing, ping, and find what's broken. It can also read and write .pkt files without Packet Tracer open.

[Building a 3 router OSPF ring, cabling it, addressing it and pinging across it]

Twelve devices, twelve cables, OSPF across the ring and 6/6 pings, from one prompt.

There are also some ready-made labs (router on a stick, OSPF/EIGRP/RIP topologies, NAT, HSRP, EtherChannel, IPv6) that build in one call.

Install

Needs uv and Packet Tracer 9.

Register the server with your MCP client:

claude mcp add packet-tracer -- uvx --from tracerlab packet-tracer-mcp

Cursor (~/.cursor/mcp.json), VS Code (.vscode/mcp.json) and Codex take the same command:

json
{  "mcpServers": {    "packet-tracer": { "command": "uvx", "args": ["--from", "tracerlab", "packet-tracer-mcp"] }  }}

Then install the Packet Tracer side once:

uvx tracerlab install-extension

Restart Packet Tracer and answer Yes when it asks about the new script module. A small "PT-MCP Bridge" window shows up and goes green once the MCP server is running.

If something isn't connecting, run uvx tracerlab doctor.

Use

Open Packet Tracer, start Claude Code and ask for things like:

  • build a 3 router OSPF ring with a PC on each LAN and ping everything
  • set up router on a stick with VLANs 10, 20, 30 and DHCP
  • what's wrong with this network
  • show me the running config on R1

examples/enterprise-two-site.pkt is a bigger network built entirely through the tools.

Tests

uv run pytest

mcp-name: io.github.atharv-santosh/tracerlab

Source: README.md at commit 17f45fc

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.6LatestOct 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts