moqtap CLI
Real-time MoQT traffic inspection, debugging, and discovery. Intercept traffic between client and relay, or peek directly into a relay to probe, discover, and inspect — all from the terminal.
Two modes, one tool
Intercept to observe existing sessions passively. Peek to actively query a relay and inspect what it's serving.
Intercept
A transparent proxy that sits between your MoQT client and relay. See control messages, stream lifecycle, objects, datagrams, and errors.
- Live frame-by-frame decoding
- Color-coded directional output (C→R / R→C)
- Session recording to .moqtrace files
- Filtering by control, data, or session ID
- JSON output for piping to jq
- WebTransport support (listen and upstream)
Peek
A lightweight MoQT client that connects directly to a relay to probe its capabilities, discover namespaces and tracks, and retrieve sample data.
- Relay info & draft version detection
- Namespace discovery
- Track enumeration via catalog
- Data retrieval (latest group or object)
- Media format detection (JSON, fMP4, LOC, MSF)
- Pipeable raw output and JSON mode
Intercept mode
Peek mode
Connect directly to a relay. Probe, discover, inspect — with a subcommand hierarchy that's easy to remember.
Relay URL resolved from inline argument, MOQTAP_RELAY env, or .moqtap.toml config.
Relay configuration
- Inline URL in command
MOQTAP_RELAYenv var.moqtap.toml(walks up directories)- User config (~/.config/moqtap/)
quic://— native QUICmoqt://— native QUIC (alias)wt://— WebTransporthttps://— WebTransport
Frequently asked questions
What is the moqtap CLI?
What is intercept mode?
What is peek mode?
How do I configure the relay URL?
Which MoQT draft versions are supported?
Is the CLI free?
See inside the protocol
Every command and flag is in the CLI reference. For MoQT over WebTransport in a page, the WebTransport Inspector brings the same decoding to your browser's DevTools.