Packet Tracer MCP — Node.js port
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PT_MCP_UI_MODE | No | Device-panel presentation mode. Valid values are 'headless' or 'ui'. A saved mode file next to the token file takes precedence over this variable. | headless |
| PT_MCP_WORKDIR | No | Working directory where exports, screenshots, and saved plans are stored. | ~/PacketTracerMCP |
| PT_MCP_BRIDGE_HOST | No | Bind address for the Packet Tracer bridge. The configured host:port is automatically added to the bridge's Host allowlist. When unset, behavior is identical to upstream and binds to loopback only. | 127.0.0.1 |
| PT_MCP_BRIDGE_TOKEN | No | Shared secret between the MCP server and the Packet Tracer extension. Must be at least 32 characters from [A-Za-z0-9_-]; an unusable value is a hard startup error. When unset, a random token is generated once and persisted to a token file. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessSyncing