stdout-mcp-server logo

stdout-mcp-server

by MCP-Mirror

The stdout-mcp-server captures and manages stdout logs through a named pipe system, making them available for debugging and analysis. It's particularly useful for monitoring application output in real-time and providing an MCP interface to query, filter, and analyze logs.

View on GitHub

Last updated: N/A

What is stdout-mcp-server?

The stdout-mcp-server is a Model Context Protocol (MCP) server that captures standard output (stdout) logs from applications by creating and monitoring a named pipe. It stores a history of recent log entries and provides tools to query, filter, and analyze these logs through an MCP client.

How to use stdout-mcp-server?

Applications redirect their stdout to the named pipe created by the server. The server captures these logs. You can then use an MCP client (like Cursor) to query and filter the logs using the available tools, such as get-logs.

Key features of stdout-mcp-server

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

Use cases of stdout-mcp-server

  • Capturing logs from multiple processes for debugging in Cursor IDE

  • Monitoring application output in real-time

  • Providing an MCP interface to query, filter, and analyze logs

  • Centralized logging for applications without built-in logging features

FAQ from stdout-mcp-server

Where is the named pipe located on Unix/MacOS?

The named pipe is located at /tmp/stdout_pipe.

Where is the named pipe located on Windows?

The named pipe is located at \\.\pipe\stdout_pipe.

What is the default number of log entries stored?

The server maintains a history of the last 100 log entries by default.

What is the get-logs tool used for?

The get-logs tool is used to retrieve logs from the named pipe with optional filtering by number of lines, text, or timestamp.

What are the system requirements?

Node.js v18 or newer is required.