stdout-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is stdout-mcp-server?

stdout-mcp-server is a Model Context Protocol (MCP) server designed to capture and manage stdout logs through a named pipe system, facilitating real-time monitoring and debugging of applications.

how to use stdout-mcp-server?

To use stdout-mcp-server, set up a named pipe for your application logs and redirect the output to this pipe. You can then use MCP tools to query and analyze the logs captured by the server.

key features of stdout-mcp-server?

  • Named pipe creation and monitoring for log capture
  • Real-time log storage and retrieval
  • Log filtering and querying capabilities
  • Cross-platform support for Windows and Unix-based systems

use cases of stdout-mcp-server?

  1. Capturing logs from multiple applications for debugging in Cursor IDE.
  2. Monitoring application output in real-time for performance analysis.
  3. Analyzing logs for error tracking and resolution.

FAQ from stdout-mcp-server?

  • Can stdout-mcp-server capture logs from any application?

Yes! Any application that can redirect its output can send logs to the named pipe.

  • Is stdout-mcp-server compatible with all operating systems?

Yes! It supports both Windows and Unix-based systems.

  • How many log entries can stdout-mcp-server store?

By default, it stores the last 100 log entries, but this can be configured.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago