get-logs
Retrieve logs from the named pipe with optional filtering
LABSCO 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
Node.js v18 or newer. The server creates the pipe itself when it starts: /tmp/stdout_pipe on macOS and Linux, \\.\pipe\stdout_pipe on Windows. Send a process's output into it with your_application > /tmp/stdout_pipe, or your_application | tee /tmp/stdout_pipe to keep seeing it in the terminal too; the server keeps the last 100 entries.
Setup effort
One command — npx -y stdout-mcp-server
USE CASES
01
Checking what a background process printed while you were elsewhere
The output was written to the pipe as it happened, so it is there to read afterwards rather than lost with the terminal.
02
Finding the error in a long log without scrolling through it
A text filter narrows the pipe's contents to the lines that mention what you are chasing.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
- npx on PATH
- Node.js v18 or later
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"stdout-mcp-server": {
"command": "npx",
"args": [
"-y",
"stdout-mcp-server"
]
}
}
}npx
TERMINAL
npx -y stdout-mcp-server
