POX MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POX_SERVER_URL | No | The URL of the POX server | http://localhost:8000 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_switchesA | Get a list of all connected OpenFlow switches |
| get_switch_descC | Get detailed information about a specific switch |
| get_flow_statsC | Get flow statistics from a switch |
| set_tableC | Set the flow table on a switch |
| append_insightC | Add a network insight to the configuration memo |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| pox-network-manager | A prompt to help you manage OpenFlow networks using POX |
| simple-hub | Configure a switch to act as a simple hub that forwards all packets to all ports |
| learning-switch | Configure a switch to act as a learning L2 switch |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Network Configuration Memo | A document containing network topology, configurations, and insights |
| Network Topology | Current network topology with connected switches |
TDQS
Scored across 5 tools
Each tool targets a distinct operation: listing switches, getting switch details, getting flow stats, setting the flow table, and appending an insight. No overlapping purposes.
All tool names follow a consistent verb_noun pattern in snake_case (append_insight, get_*, set_table), making them predictable and easy to understand.
With 5 tools, the server is well-scoped for its purpose of OpenFlow switch management. The number falls within the ideal range and each tool provides necessary functionality.
The set covers basic operations like querying and setting but lacks tools for deleting or modifying flow rules, or managing switch connections, leaving notable gaps for full lifecycle management.