Documentation Index
Fetch the complete documentation index at: https://docs.q-uestionable.ai/llms.txt
Use this file to discover all available pages before exploring further.
qai proxy
Intercept and replay MCP traffic for inspection, testing, and analysis.
qai proxy [COMMAND] [OPTIONS]
Commands
proxy start
Start the proxy with an interactive TUI.
qai proxy start --transport TRANSPORT [OPTIONS]
| Option | Required | Type | Description |
|---|
--transport | Yes | string | Transport type: stdio, sse, or streamable-http |
--target-command | When transport is stdio | string | Server command to proxy (stdio only) |
--target-url | When transport is sse or streamable-http | string | Server URL to proxy (HTTP transports only) |
--intercept | No | flag | Start in intercept mode (default: passthrough) |
--session-file | No | string | Auto-save session to this file on exit |
qai proxy start \
--transport stdio \
--target-command "python my_server.py" \
--intercept
Use passthrough mode (default) for passive capture of complete interactions. Use intercept mode when you need to halt and inspect or modify specific messages.
proxy replay
Replay captured messages against a live server.
qai proxy replay --session-file FILE [OPTIONS]
| Option | Required | Type | Description |
|---|
--session-file | Yes | string | Path to saved session file |
--target-command | Yes* | string | Server command for replay (stdio) |
--target-url | Yes* | string | Server URL for replay (SSE/HTTP) |
--output | No | string | Save replay results to JSON file |
--timeout | No | float | Per-message response timeout in seconds (default: 10.0) |
--no-handshake | No | flag | Skip auto-handshake; session must start with initialize |
--target-command or --target-url is required.
Examples:
qai proxy replay \
--session-file session.json \
--target-command "python my_server.py" \
--output results.json
By default, the replay engine sends a synthetic initialize handshake before replaying messages. Use --no-handshake if your session already includes the full handshake sequence.
proxy export
Export a session to JSON.
qai proxy export --session-file FILE --output OUTPUT [OPTIONS]
| Option | Required | Type | Description |
|---|
--session-file | Yes | string | Path to saved session file |
--output | Yes | string | Output file path |
--output-format | No | string | Export format (default: json) |
qai proxy export \
--session-file session.json \
--output report.json
proxy inspect
Print session contents to stdout for review.
qai proxy inspect --session-file FILE [OPTIONS]
| Option | Required | Type | Description |
|---|
--session-file | Yes | string | Path to saved session file |
--verbose, -v | No | flag | Show full JSON payloads for each message |
qai proxy inspect --session-file session.json -v
Session: abc-123
Transport: stdio
Server command: python my_server.py
Messages: 12
#000 → initialize id=1
#001 ← (response) id=1
#002 → notifications/initialized
#003 → tools/call id=2
-v to include full JSON payloads.
Message Direction
In inspect output:
→ denotes client-to-server messages (requests and notifications sent to the server)← denotes server-to-client messages (responses and notifications from the server)
In the TUI (proxy start):
▶ denotes client-to-server messages◀ denotes server-to-client messages⏸ prefix on held messages (intercept mode)✕ prefix on dropped messages
Exit Codes
| Code | Meaning |
|---|
| 0 | Success |
| 1 | Command error (invalid options, file not found, validation failure) |
| 130 | Interrupted by user (Ctrl+C) |