# Output MCP tools

Output tools inspect Solo's saved terminal output and discovered ports without requiring the MCP client to scrape the UI.

## Tools

- `get_process_output` — Read recent rendered terminal output.
- `get_process_raw_output` — Read recent retained terminal output as lossy UTF-8 text. Solo strips ANSI CSI and OSC sequences, splits the text into lines, selects the requested tail, and rejoins it with newlines; this is not a byte-preserving raw stream.
- `search_output` — Search rendered terminal output for matching lines.
- `search_raw_output` — Search retained terminal-output lines after lossy UTF-8 decoding and ANSI CSI/OSC removal. Some other control characters can remain.
- `clear_output` — Clear Solo's saved output for a process without touching the PTY.
- `get_process_ports` — List detected localhost ports and localhost or safe local-development `.test` URLs for a process. Useful for [service discovery](./services.md) and readiness checks.

## Notes

Use rendered output for ordinary diagnostics. The retained-output tools can expose text hidden by terminal rendering, but their lossy decoding, ANSI removal, and line handling make them unsuitable for inspecting escape sequences or as a byte-preserving terminal-protocol trace. Clearing output only clears Solo's saved output buffer; it does not stop the running process.

See [Debug a live application with an agent](../workflows/debug-live-application.md) for a complete workflow that combines output inspection, port discovery, reproduction, and verification.

---

Are you a human? Read this doc on the web: https://soloterm.com/docs/mcp-tools/output