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.
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:
{
"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
Metadata
Release files for tracerlab 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tracerlab-0.1.6.tar.gz | 163.3 kB | With provenance | Details for tracerlab-0.1.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tracerlab-0.1.6-py3-none-any.whl | Python 3 | none | any | Details for tracerlab-0.1.6-py3-none-any.whl |
Total release size: 319.4 kB
Release files / tracerlab-0.1.6.tar.gz
| Download URL | tracerlab-0.1.6.tar.gz |
|---|---|
| Size | 163.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f054b03dd2e3b452fd01138953d32efa89c4fd224a3d2cb22787d1fecfbbfa3a
|
|
BLAKE2b-256 checksum How to use checksums |
343724fdbed3fb7c396b174fbfcadb1a7001a5e28c679e5d9ad328ce96771930
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logRelease files / tracerlab-0.1.6-py3-none-any.whl
| Download URL | tracerlab-0.1.6-py3-none-any.whl |
|---|---|
| Size | 156.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2cad6c480830ba3668b4f674f21bcf4e8155ae9b2be36bc624d7789e4f056ad9
|
|
BLAKE2b-256 checksum How to use checksums |
feabe2909007610875d53836d549955331c6a4c907b123cffdfb309815f30107
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logSecurity for tracerlab 0.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for tracerlab-0.1.6.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.