This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and
Pox MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project.
A Model Context Protocol (MCP) server implementation that provides network control and management capabilities through the POX SDN controller. This server enables Python-based network programming, OpenFlow device management, and automated network analysis through POX's modular architecture. Perfect for educational environments, network prototyping, and SDN research.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Once Pox is connected, these are the calls the assistant has available:
get_switches — List all connected OpenFlow datapathsReturns — Array of active POX-controlled switchesget_switch_desc — Get detailed datapath informationInput — - dpid (string): Datapath identifierget_flow_stats — Retrieve POX flow statisticsset_table — Configure POX flow tablesappend_insight — Add network insights to POX configuration memoResources — The server exposes two dynamic resources: - pox://network-config: A comprehensive POX controller configuration memo - Tracks active POX componentsPrompts — The server provides three specialized prompts: - pox-network-manager: Interactive prompt for POX controller management - Required argument: topic -Tools — The Tools tool exposed by this serverYou will need one environment variable: POX_SERVER_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pox's toolset — get_switches, Returns, get_switch_desc and 7 more — is a fair guide to whether it matches your workflow. It is maintained by davidlin2k; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Pox's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get_switches | List all connected OpenFlow datapaths |
| Returns | Array of active POX-controlled switches |
| get_switch_desc | Get detailed datapath information |
| Input | - dpid (string): Datapath identifier |
| get_flow_stats | Retrieve POX flow statistics |
| set_table | Configure POX flow tables |
| append_insight | Add network insights to POX configuration memo |
| Resources | The server exposes two dynamic resources: - pox://network-config: A comprehensive POX controller configuration memo - Tracks active POX components and their configurations - Records network topology and flow rules - Main |
| Prompts | The server provides three specialized prompts: - pox-network-manager: Interactive prompt for POX controller management - Required argument: topic - The network control aspect to focus on - Helps configure POX components |
| Tools | The Tools tool exposed by this server. |
{
"mcpServers": {
"pox": {
"command": "uv",
"args": [
"--directory",
"parent_of_servers_repo/servers/src/mcp_server_pox",
"run",
"server.py"
],
"env": {
"POX_SERVER_URL": "http://localhost:8000"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| POX_SERVER_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.