An MCP server that any process can pipe stdout logs to including console logs from nodejs programs
{
"mcpServers": {
"stdout-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 397 days ago. 7 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Context cost
1 tool. ~100 tokens (0.1% of 200K).
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
get-logsRetrieve logs from the named pipe with optional filtering
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for Stdout Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that captures and manages stdout logs through a named pipe system. This server is particularly useful for:
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:
your_application | tee /tmp/stdout_pipe # or
your_application > /tmp/stdout_pipe
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
Before installing, please ensure you have:
Cursor > Settings > MCP Serversname: stdout-mcp-server
type: command
command: npx stdout-mcp-server
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"]
}
}
}
To send your application's output to the pipe:
# Unix/MacOS
your_application > /tmp/stdout_pipe
# Windows (PowerShell)
your_application > \\.\pipe\stdout_pipe
You can redirect logs from multiple sources:
# Application 1
app1 > /tmp/stdout_pipe &
# Application 2
app2 > /tmp/stdout_pipe &
Your AI will use the get-logs tool in your MCP client to retrieve and filter logs:
// Get last 50 logs
get-logs()
// Get 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
\\.\pipe\stdout_pipe/tmp/stdout_pipeRetrieve 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 afterExample 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"
}]
}
MIT License