Autonomous port recovery with Junos MCP

The problem

A flapping port on a backbone router usually means a 3am page for someone. The goal of Junos MCP Server is to remove the human from that loop.

The loop

The agent runs a tight observe → decide → act cycle:

1. Poll interface state over NETCONF/PyEZ
2. Correlate CRC errors and last-flap timers
3. Decide whether a safe bounce will help
4. Apply the change and verify recovery

agent> set interfaces ge-0/0/3 disable; commit
commit complete
agent> delete interfaces ge-0/0/3 disable; commit
ge-0/0/3 oper-status UP — recovered autonomously

Why MCP

The Model Context Protocol gives the model a small, audited set of tools instead of raw shell access — so every action is bounded and logged.