Local Logs MCP Server
Related Servers
Alternatives to Local Logs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to automatically inspect and analyze application runtime log files for debugging and troubleshooting. Supports monitoring multiple log directories simultaneously with tools for listing, reading, searching, and paginating through log files.8MIT
- FlicenseNot gradedqualityDmaintenanceHandles log file management and analysis with tools to list, read, search, filter, and generate analytics on log files.1-
- AlicenseNot gradedqualityDmaintenanceA 100% local development monitoring tool that captures browser console logs, network requests, and backend server output for analysis by AI assistants via MCP. It enables LLMs to debug applications by providing structured, real-time access to full-stack log data and persistent local storage.2 npm7MIT
- FlicenseNot gradedqualityDmaintenanceAnalyzes log files using AI-powered tools to detect errors, patterns, and anomalies through natural language queries in Cursor IDE.-
- AlicenseNot gradedqualityDmaintenanceMCP server for collecting and analyzing CLI/web server error logs. Enables watching log files/directories, parsing common error patterns, and querying/analyzing logs through natural language.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read and analyze Linux system logs—including systemd journal, syslog, kernel, application, and Docker container logs—for diagnostics and predictive analysis.MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: get_errors retrieves error entries, get_log_files lists files, get_server_status provides a summary, search_logs finds text, tail_log gets last lines, and watch_log monitors changes. The descriptions reinforce these unique functions, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern using snake_case, such as get_errors, search_logs, and tail_log. This uniformity makes the set predictable and easy to understand, with no deviations in naming style.
With 6 tools, the server is well-scoped for log management, covering essential operations like listing, searching, tailing, and monitoring logs. Each tool earns its place without being excessive or insufficient for the domain.
The tool set provides strong coverage for log reading and monitoring, including search, tail, and watch functionalities. A minor gap exists in write operations (e.g., clearing or modifying logs), but agents can effectively work with the provided read-only tools for typical log analysis tasks.