Packet Tracer Visual MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ptv_bridgeStatusA | Check whether the Packet Tracer Visual MCP extension is connected. |
| ptv_getNetworkA | Read the current Packet Tracer logical workspace: devices, interfaces, and links. |
| ptv_addDeviceC | Add one Packet Tracer device at a specific workspace coordinate. |
| ptv_addDevicesTimelineB | Add devices one by one inside Packet Tracer with a short delay between real add operations. Use for screen recordings where viewers should see devices appear sequentially. |
| ptv_addLinkC | Create one link between two existing Packet Tracer interfaces. |
| ptv_addLinksTimelineC | Create links one by one with a short delay, optimized for recording a topology being wired. |
| ptv_configurePcC | Set a PC or Server IPv4 address, mask, gateway, DNS, or DHCP flag. |
| ptv_configureIosC | Send Cisco IOS commands to one router or switch. Commands may be a string or an array of strings. |
| ptv_getCommandLogB | Read recent Packet Tracer command history for one device or the whole workspace. |
| ptv_runShowCommandsA | Issue show commands to one IOS device and return command-log confirmation. Packet Tracer does not guarantee full show-output parsing. |
| ptv_probeDeviceApiA | Read-only probe for Packet Tracer device object APIs. Use it to inspect whether a device exposes service-related methods before implementing Server-PT automation. |
| ptv_probeServerServicesB | Read-only probe for Server-PT service automation hints. It scans one Server-PT or all Server-PT devices for DNS/HTTP/FTP/DHCP related API names without changing services. |
| ptv_generateIosTemplateC | Generate reusable IOS command templates for static routes, RIP, OSPF, EIGRP, DHCP pools, extended ACLs, and NAT/PAT. This does not touch Packet Tracer. |
| ptv_generateCampusValidationPlanB | Generate a campus validation plan. Default validationMode is fast, which avoids show-command sweeps. Use standard or strict only when slower IOS command checks are acceptable. |
| ptv_validateCampusFastB | Run a speed-preserving campus validation: plan shape, build/apply results, one optional canvas snapshot, and key-device/link checks. It does not run heavy show commands. |
| ptv_generateCampusIosConfigA | Generate a complete IOS configuration set for the built-in campus topology. Supports routingProtocol static/rip/ospf/eigrp, IOS DHCP pools, ACL templates, and NAT/PAT. |
| ptv_applyCampusIosConfigC | One-click generation and application of the complete campus IOS configuration set. Requires the Packet Tracer bridge to be connected. |
| ptv_applyIosConfigSetC | Apply an arbitrary IOS config set made of deviceName plus commands entries. |
| ptv_getFaultLibraryA | List built-in fault injection scenarios and their expected symptoms and verification commands. |
| ptv_injectFaultC | Generate or apply a built-in fault scenario, such as missing trunk VLAN, OSPF area mismatch, missing static route, overblocking ACL, or broken NAT outside marking. |
| ptv_repairFaultC | Generate or apply the repair commands for a built-in fault scenario. |
| ptv_getCampusPlanA | Generate the built-in campus-network demo plan without touching Packet Tracer. Use this to preview device names, VLANs, links, service steps, and tests. |
| ptv_buildCampusRecordingDemoC | Build a visually complex campus topology in Packet Tracer: devices appear sequentially, links are drawn sequentially, PC/server IPs are applied, and IOS commands are optionally sent. Designed for course-design demos and screen recordings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lyf94697-droid/packet-tracer-visual-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server