PT Tutor
Provides a troubleshooting tutor for Cisco Packet Tracer labs by reading the live network topology and device state, running read-only diagnostic commands such as show, ping, and traceroute, diagnosing reachability faults, and offering layered hints without revealing or applying configurations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@PT Tutor PC1 can't ping the server — help me find the fault"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PT Tutor
A troubleshooting tutor for Cisco Packet Tracer, built on the Model Context Protocol.
It reads the student's live network, finds the fault, and teaches them to find it too.
Most AI tools for Packet Tracer build and fix the lab for you. PT Tutor does the opposite: it works out what's wrong, then asks the next good question, the way a lab instructor would. The student makes every change.
Features
Read-only by design. Only status commands (
show,ping,traceroute,ipconfig) can run. Configuration commands are refused.Real diagnosis. It walks the path in both directions (cabling, interfaces, VLANs, trunks, gateways, routes, ACLs, DHCP) and checks its verdict with a live ping.
Hint ladder. Every finding has three levels: a nudge, a pointer to where to look, then the concept. No level hands over the configuration.
Assessment guard. If a graded activity (
.pka) is open, it switches to hint-only mode. It says where the problem is, not what it is. If it can't tell whether the file is graded, it assumes it is.
Related MCP server: ptlab
How it works
Claude ──MCP──▶ PT Tutor server ──file mailbox──▶ Packet Tracer script module
(Node.js) ~/.pt-tutor (reads the live network)A small script module inside Packet Tracer exchanges files with the server in ~/.pt-tutor/mailbox. It opens no network port, and it accepts only a short list of read-only commands.
Getting started
Requirements: Packet Tracer 9.0, Node.js 20 or newer, and an MCP client such as Claude Code or Claude Desktop.
1. Get the Packet Tracer module
npx -y pt-tutor-mcp bridgeThis saves pt-tutor-bridge.pts in the current folder.
2. Add it to Packet Tracer
Open Extensions → Scripting → Configure PT Script Modules.
Click Add and choose
pt-tutor-bridge.pts.Give the module file access in its permission settings, then start it.
3. Connect your MCP client
claude mcp add pt-tutor -- npx -y pt-tutor-mcpFor Claude Desktop, add it to claude_desktop_config.json:
{
"mcpServers": {
"pt-tutor": { "command": "npx", "args": ["-y", "pt-tutor-mcp"] }
}
}4. Try it. Open a lab, break something, and ask for help. In Claude Code, run:
/mcp__pt-tutor__tutor PC1 can't reach the serverTools
Tool | Purpose |
| Connection check, the open file, and the current tutor mode |
| Devices, ports and links on the canvas |
| Interfaces, addresses, routes and VLANs of one device |
| One read-only command on a device |
| Why a source can't reach a destination (10–60 s) |
| The next hint for a finding |
For instructors
Set PT_TUTOR_MODE in the server's env:
Value | Behaviour |
| Hint-only during graded activities, full hints otherwise |
| Hint-only for every lab |
An unrecognised value also means hint-only, so a typo can't turn the guard off. The setting lives in the MCP config, so on shared machines keep that file somewhere students can't edit.
Limitations
Packet Tracer 9 only. Developed on macOS; Windows and Linux are untested.
Static routing, VLANs, trunks and ACLs are checked in depth. OSPF and EIGRP are read from the routing table only.
The commands the tutor runs appear in the device's console history.
Development
git clone https://github.com/faithere1/pt-tutor-mcp.git && cd pt-tutor-mcp
npm install
npm test # build and run the test suite (no Packet Tracer needed)
node tools/build-release.mjs # write the release bridge with dev commands offSee PROGRESS.md for the architecture, the dev setup and the Packet Tracer API notes.
Getting help
Found a bug or a wrong diagnosis? Open an issue. Contributions are welcome; see CONTRIBUTING.md.
License
Available Tools
6 toolsdiagnoseDiagnose connectivityARead-only
Explain why one device can or cannot reach another. Reads the whole live network (addressing, gateways, VLANs, trunks, interface state, routing tables, static routes, ACLs, proxy ARP), walks the path hop by hop in both directions, and runs a real ping to confirm. Returns findings with a code, the device and interface, evidence and the concept involved. In tutor mode, use the findings to ask guiding questions; do not paste the fix. Pass a finding to tutor_hint to get a graded hint. In hint-only mode the findings are redacted to where the problem is (device, interface, area) and a ref for tutor_hint. Takes 10-60 seconds on larger labs.
Inputs: source (required), destination (required), ping.
get_device_stateGet device stateARead-only
Detailed state of one device: every port (IP, mask, MAC, admin and line status, neighbour), plus the key show output for its kind. Routers get 'show ip interface brief' and 'show ip route'. Switches add 'show vlan brief' and 'show interfaces trunk'. End devices get 'ipconfig /all'. Read-only.
Inputs: device (required).
get_topologyGet network topologyARead-only
List every network device on the Packet Tracer canvas (name, type, model, power) with its cabled or addressed ports, and every link with its up/down state. Read-only.
Inputs: includeNonNetwork.
pt_statusPacket Tracer statusARead-only
Check that Packet Tracer is connected and report its version, the open file, and whether that file is a graded activity (.pka). Call this first. tutorMode is "hint-only" during a graded activity or when an instructor has set it for every lab (hintOnlyReason says which): diagnose hides what is wrong, hints stop at level 2, and the configuration can't be read. Guide them with questions; never give the configuration that solves the activity.
Inputs: no named parameters.
run_commandRun a read-only commandARead-only
Run one read-only command on a device's terminal and return its output. IOS devices (routers, switches) accept 'show ...', 'ping' and 'traceroute'. End devices (PCs, servers) accept 'ipconfig', 'ping', 'tracert', 'arp -a', 'nslookup' and 'netstat'. Configuration commands are refused: the student makes the changes, the tutor only looks. In hint-only mode, 'show running-config' and 'show startup-config' are refused too.
Inputs: device (required), command (required).
tutor_hintGet a tutor hintARead-only
Get a hint for a finding from diagnose, at one of three levels. Pass either the finding's code, or its ref when diagnose returned redacted findings. Level 1 is a nudge towards the problem area without naming the device. Level 2 names the device and a read-only command to look at. Level 3 explains the concept. No level gives the fix. Start at level 1 and only go up after the student has tried and is still stuck. Put the hint in your own words, as a question where you can. In hint-only mode the highest level is 2.
Inputs: level (required), ref, code, device, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes: status, topology, per-device state, command execution, diagnosis, and hints. The main overlap is between get_device_state and run_command, since both can return show output, but their descriptions clarify aggregate state versus a single read-only command.
The names are all readable snake_case, but the conventions are mixed: get_topology/get_device_state/run_command use verb_noun, while pt_status, diagnose, and tutor_hint do not. This is not chaotic, but it is not a predictable verb_noun pattern throughout.
Six tools is well-scoped for a read-only Packet Tracer tutoring workflow. Each tool has a distinct role in the inspection, diagnosis, and hinting flow.
The toolset covers connection status, topology, device state, command inspection, diagnosis, and leveled hints, which is a coherent read-only lifecycle. Minor gaps might include retrieving activity instructions or broader lab context, but the core tutoring and diagnostic surface is present.
Maintenance
Related MCP Connectors
Network, domain and website diagnostics for AI clients via MCP.
Remote MCP server for deterministic educational practice-assessment score conversions.
MCP diagnostics that help AI agents find safe next steps for HTTP, API, and MCP failures.
Remote MCP for A2A failure replay MCP, structured receipts, audit logs, and reviewer-ready evidence.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables network troubleshooting through an MCP Streamable HTTP endpoint, exposing diagnostic tools for Cisco Packet Tracer labs with human-in-the-loop review and NIST/CIS security validation.-
- AlicenseAqualityCmaintenanceEnables headless creation, parsing, and grading of Cisco Packet Tracer .pkt/.pka lab files, including CCNA activity scoring, through MCP tools without requiring Packet Tracer to run.6MIT

Network Lab MCPofficial
AlicenseAqualityBmaintenanceEnables MCP-capable AI clients to inspect live lab topology, manage terminal sessions, run commands, collect evidence, and support network investigation, troubleshooting, and validation while engineers retain control over managed definitions and decisions.7Apache 2.0- AlicenseBqualityBmaintenanceEnables MCP clients to build and troubleshoot Cisco Packet Tracer networks by adding devices, cabling them, pushing IOS configurations, addressing interfaces, configuring routing, running pings, and reading/writing .pkt files without Packet Tracer open.4262 PyPIMIT