Labsco
amitdeshmukh logo

stdout-mcp-server

โ˜… 7

from amitdeshmukh

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

๐Ÿ”ฅ๐Ÿ”ฅ๐Ÿ”ฅโœ“ VerifiedFreeQuick setup

stdout-mcp-server

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

How It Works

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

  2. 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
  1. The server monitors the pipe, captures all incoming logs, and maintains a history of the last 100 entries

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

Features

  • 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)

Named Pipe Locations

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

Available Tools

get-logs

Retrieve logs from the named pipe with optional filtering:

Parameters:

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

Example responses:

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