Local Logs
This local logs monitoring MCP server by mariosss provides real-time log file access and analysis for development and production environments through six specialized tools including log tailing, error tracking, file listing, server status analysis, log watching, and text search capabilities. Built with Node.js and featuring automatic log directory detection across multiple project structures (monorepos, backend folders, system logs), it offers cross-platform support with memory-efficient streaming for large files, configurable log extensions via environment variables, and read-only access for security. The implementation uses JSON-RPC 2.0 over stdio communication and includes fallback mechanisms for both Unix tail commands and pure JavaScript file reading, making it valuable for developers debugging applications, DevOps teams monitoring server health, and AI assistants that need to analyze log patterns and troubleshoot issues across different deployment environments.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.
Scan details: Circle-IR · 2026-09-28 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- devops-ci
- Source
- PulseMCP
- Repository
- github.com/mariosss/local-logs-mcp-server
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
Use via MCP
Resolve Local Logs from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.