StdoutMCP

Captures and manages stdout logs from multiple processes via a named pipe system for real-time debugging and analysis.

A Model Context Protocol (MCP) server that captures and manages stdout logs through a named pipe system. This server is particularly useful for:

- Capturing logs from multiple processes or applications and making them available for debugging in Cursor IDE.
- Monitoring application output in real-time and providing a MCP interface to query, filter, and analyze logs
-

The server creates a named pipe at a specific location (/tmp/stdout_pipeon Unix/MacOS or\\.\pipe\stdout_pipeon Windows)

Any application can write logs to this pipe using standard output redirection. For example:

your_application | tee /tmp/stdout_pipe # or your_application > /tmp/stdout_pipe

-

The server monitors the pipe, captures all incoming logs, and maintains a history of the last 100 entries

Through MCP tools, you can query, filter, and analyze these logs

Before installing, please ensure you have:
- Open Cursor and navigate toCursor > Settings > MCP Servers
- Click on "Add new MCP Server"
- Update your MCP settings file with the following configuration:

name: stdout-mcp-server type: command command: npx stdout-mcp-server

Option 2: Installation in other MCP clients

{ "mcpServers": { "stdio-mcp-server": { "command": "npx", "args": [ "stdio-mcp-server" ] } } }

{ "mcpServers": { "mcp-installer": { "command": "cmd.exe", "args": ["/c", "npx", "stdio-mcp-server"] } } }

To send your application's output to the pipe:

# Unix/MacOS your_application > /tmp/stdout_pipe # Windows (PowerShell) your_application > \\.\pipe\stdout_pipe

You can redirect logs from multiple sources:

# Application 1 app1 > /tmp/stdout_pipe & # Application 2 app2 > /tmp/stdout_pipe &

Your AI will use theget-logstool in your MCP client to retrieve and filter logs:

// Get last 50 logs get-logs() // Get last 100 logs containing "error" get-logs({ lines: 100, filter: "error" }) // Get logs since a specific timestamp get-logs({ since: 1648675200000 }) // Unix timestamp in milliseconds

- Named pipe creation and monitoring
- Real-time log capture and storage
- Log filtering and retrieval through MCP tools
- Configurable log history (default: 100 entries)
- Cross-platform support (Windows and Unix-based systems)

- Windows:\\.\pipe\stdout_pipe
- Unix/MacOS:/tmp/stdout_pipe

Retrieve logs from the named pipe with optional filtering:

- lines(optional, default: 50): Number of log lines to return
- filter(optional): Text to filter logs by
- since(optional): Timestamp to get logs after

// Response format { content: [{ type: "text", text: "[2024-03-20T10:15:30.123Z] Application started\n[2024-03-20T10:15:31.456Z] Connected to database" }] }

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Seamlessly bring real-time production context—logs, metrics, and traces—into your local environment to auto-fix code faster.

AI-powered live runtime debugging with Lightrun production context.

Debug and investigate app issues using AI and Grafana Loki

Analyze your MCP setup: measure token cost per tool, find bloated schemas, detect duplicates, and get optimization tips to reclaim your context window.

MCP server for .NET runtime diagnostics — memory, GC, threads, and more.

MCP server for .NET runtime diagnostics — memory, GC, threads, and more.

JVM diagnostics MCP server for thread dump and GC log analysis. Detects deadlocks, lock contention, and GC pressure. Runs via npx on Node.js — no JVM or Docker required.

Reticle intercepts, visualizes, and profiles JSON-RPC traffic between your LLM and MCP servers in real-time, with zero latency overhead. Stop debugging blind. Start seeing everything.

PawSift bridges Android Logcat to LLMs in a token-efficient way

Turn natural language into powerful Perfetto trace analysis. Quickly explain jank, diagnose ANRs, spot CPU hot threads, uncover lock contention, and find memory leaks.