Integrations
Provides support for capturing stdout logs from applications running on Unix/Linux systems through a named pipe at /tmp/stdout_pipe.
Enables monitoring of application output on macOS systems through a named pipe at /tmp/stdout_pipe, allowing real-time log capture and analysis.
Serves as a runtime requirement for the server with Node.js v18 or newer needed to run the MCP server.
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
- The server creates a named pipe at a specific location (
/tmp/stdout_pipe
on Unix/MacOS or\\.\pipe\stdout_pipe
on Windows) - Any application can write logs to this pipe using standard output redirection. For example:
- 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
System Requirements
Before installing, please ensure you have:
- Node.js v18 or newer
Installation Options
Option 1: Installation in Cursor
- Open Cursor and navigate to
Cursor > Settings > MCP Servers
- Click on "Add new MCP Server"
- Update your MCP settings file with the following configuration:
Option 2: Installation in other MCP clients
Installation in other MCP clients
For macOS/Linux:
For Windows:
Usage Examples
Redirecting Application Logs
To send your application's output to the pipe:
Monitoring Multiple Applications
You can redirect logs from multiple sources:
Querying Logs
Your AI will use the get-logs
tool in your MCP client to retrieve and filter 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 returnfilter
(optional): Text to filter logs bysince
(optional): Timestamp to get logs after
Example responses:
License
MIT License
This server cannot be installed
local-only server
The server can only run on the client's local machine because it depends on local resources.
A Model Context Protocol server that captures and manages stdout logs through named pipes, making application output available for querying and debugging in AI tools like Cursor IDE.
Related MCP Servers
- -securityFlicense-qualityA Model Context Protocol server that enables AI assistants to explore and interact with Cursor IDE's SQLite databases, providing access to project data, chat history, and composer information.Last updated -10Python
- AsecurityAlicenseAqualityA Model Context Protocol server that provides programmatic access to the Windows terminal, enabling AI models to interact with the Windows command line through standardized tools for writing commands, reading output, and sending control signals.Last updated -3JavaScriptMIT License
- AsecurityFlicenseAqualityA starter template for building Model Context Protocol servers that can be integrated with Cursor or Claude Desktop, allowing developers to create custom tools and extensions for AI assistants.Last updated -169TypeScript
- -securityFlicense-qualityA Model Context Protocol server that provides AI assistants with structured access to your Logseq knowledge graph, enabling retrieval, searching, analysis, and creation of content within your personal knowledge base.Last updated -19TypeScript