Summary
Output from a process nobody is watching becomes readable without tailing a terminal.
The pipe is the whole interface: anything that writes into it becomes queryable through one tool, so a dev server, a build watcher and a background job can all report into the same place. The three parameters are what keep that usable — matching text, a line count and a starting point, which is the difference between the twenty lines that matter and an entire session's noise.
What it is
A single-tool reader over a named pipe that collects process output.
What you get
- Logs read back from the named pipe, filtered by matching text, limited to a number of lines, or restricted to what arrived since a given point.
Requirements
A named pipe that your processes write their output into, so there is something on the other end to read.
Setup effort
One command — npx -y stdout-mcp-server