Amitdeshmukh Stdout MCP Server

🚀 stdout-mcp-server

A Model Context Protocol (MCP) server that captures and manages standard output logs through the named pipe system. This server is particularly suitable for:

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

🚀 Quick Start

How It Works

1. The server creates a named pipe at a specific location (/tmp/stdout_pipe for Unix/MacOS systems and \\.\pipe\stdout_pipe for Windows systems).
2. Any application can write logs to this pipe by redirecting standard output. For example:

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

3. The server monitors the pipe, captures all incoming logs, and maintains a history of the last 100 records.
4. You can query, filter, and analyze these logs through the MCP tool.

System Requirements

Before installation, ensure you have:

• Node.js v18 or higher

Installation Options

Option 1: Install in Cursor

1. Open Cursor and navigate to Cursor > Settings > MCP Server.
2. Click "Add New MCP Server".
3. Update your MCP settings file with the following configuration:

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

Option 2: Install in Other MCP Clients

Installation examples for other systems:

For macOS/Linux:

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

For Windows:

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

💻 Usage Examples

Redirecting Application Logs

To send your application output to the pipe:

# Unix/MacOS
your_application > /tmp/stdout_pipe

# Windows (PowerShell)
your_application > \\.\pipe\stdout_pipe

Monitoring Multiple Applications

You can redirect logs from multiple sources:

# Application 1
app1 > /tmp/stdout_pipe &

# Application 2
app2 > /tmp/stdout_pipe &

Querying Logs

Your AI will use the get-logs tool in the MCP client to retrieve and filter logs:

// Get the last 50 logs
get-logs()

// Get the 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

✨ Features

• Creation and monitoring of named pipes
• Real-time log capture and storage
• Log filtering and retrieval through the MCP tool
• Configurable log history (default: 100 entries)
• Cross-platform support (Windows and Unix systems)

📚 Documentation

Named Pipe Location

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

Available Tools

get-logs

Retrieve logs from the named pipe with optional filtering:

Example response:

// Response format
{
  content: [{
    type: "text",
    text: "[2023-10-05 12:34:56] Info: System started"
  }]
}

📄 License

This project is licensed under the MIT License.