Back to docs

Proxy: controlled network fault injection for MQTT

How Proxy models runtime, toxics, recovery checks, and failure reports.

Jun 24, 2026Mqttable EngineeringMqttable Engineering

/proxy is a product surface in Mqttable. It exists because MQTT debugging needs a place for this job, not because every task should start from MCP. This page focuses on the product workflow. MCP support is a companion layer: use it when automation helps, not as the starting point for every task.

Interactive diagram

Proxy config to toxic plan to apply to recovery verify to failure report.

Placeholder for the interactive diagram. Replace with the generated artifact when ready.

placeholder

Human job

  • Create a proxy in front of a broker.
  • Add latency, bandwidth, timeout, or disconnect behavior deliberately.
  • Clean up and verify recovery before trusting the result.

Automation handoff

  • MCP and CLI are supporting surfaces here, not the whole story.
  • Use MCP reads when the same state needs to be inspected by an agent.
  • If an action changes MQTT state, use schema, plan, confirmation, apply, and verify.

Boundary

Keep this surface focused. If the job belongs to another workflow, move there instead of turning one page into everything.