stdout

This MCP server captures stdout output sent to a named pipe and exposes it via the MCP interface for querying, filtering, and analysis. It creates a named pipe at a standard location (Unix/MacOS: /tmp/stdout_pipe; Windows: \.\pipe\stdout_pipe) and collects the latest logs (default history of 100 entries). You can redirect an application's standard output to the pipe, and then use the MCP client tools to retrieve recent logs, filter by text, or request logs since a given timestamp. For example, you can redirect multiple applications to the same pipe and then query across all of them using get-logs to inspect recent activity or troubleshoot issues in real time.

Prerequisites:

• Node.js v18 or newer installed on the host
• npm or corepack available

Option 1: Installation in Cursor

1. Open Cursor and navigate to Cursor > Settings > MCP Servers
2. Click on "Add new MCP Server"
3. Update your MCP settings file with:

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

Option 2: Installation in other MCP clients

Option 2A: macOS/Linux Create or update your MCP configuration to include:

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

Option 2B: Windows Create or update your MCP configuration to include:

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

Notes:

• The server is provided as an MCP-enabled npm package and is typically run via npx as shown above.
• Ensure you have network access or the npm cache available when running first-time installations.

Tips and considerations:

• The named pipe location is platform-specific: /tmp/stdout_pipe on Unix-like systems and \.\pipe\stdout_pipe on Windows. Ensure the path is accessible by your applications.
• The server maintains a configurable history (default 100 entries). If you expect high log throughput, consider increasing the history in your MCP client configuration if supported.
• Use the get-logs tool in your MCP client to fetch logs with optional filtering, line counts, or time-based queries. Example usage includes getting the last 50 logs or filtering for the term 'error'.
• If multiple applications write to the same pipe, logs will accumulate in the single history, enabling cross-source debugging but requiring careful filtering to distinguish sources.
• Ensure the applications writing to the pipe redirect output correctly to the pipe path compatible with your OS (as shown in the README examples).
• If you run into permissions issues on the pipe, verify user permissions and the ability to create/read the named pipe in the target directory.