Installation¶
Requirements¶
| Requirement | Version | Notes |
|---|---|---|
| Python | 3.11+ | |
mcp[cli] |
≥ 1.13, < 2 | Installed automatically |
pydantic |
≥ 2.11, < 3 | Installed automatically |
| Cisco Packet Tracer | 8.2+ | Only for live deploy |
| MCP Control Center extension | latest | This project's own PT extension (.pts in Releases), only for live deploy — see Live Deploy Setup |
pydantic ≥ 2.11 is required
Modern mcp builds tool output schemas from return annotations and needs
pydantic ≥ 2.11. An older pydantic makes the server crash on startup. The
pinned dependencies handle this for you; just don't force an older pydantic.
Install the server¶
After pip install -e ., the packet_tracer_mcp module is importable from any
directory, so python -m packet_tracer_mcp --stdio works from anywhere — no need
to cd into the repo or keep a server running.
Connect your MCP client¶
Verify:
Remove later with claude mcp remove packet-tracer --scope user.
Add to your MCP config (.vscode/mcp.json or user settings):
Transport modes¶
- stdio (recommended for desktop clients): the client spawns the server as a
child process. The internal HTTP bridge to Packet Tracer (
:54321) still starts automatically inside that process — live deploy works the same. - streamable-http (
http://127.0.0.1:39000/mcp): start the server yourself withpython -m packet_tracer_mcpand let multiple clients share one instance.
On Windows, python must be on PATH
If your client can't spawn the server, use the full interpreter path in the
command field (e.g. C:\\Users\\you\\AppData\\Local\\Programs\\Python\\Python312\\python.exe).
Next: run the Quick Start example.