inspect-logs-mcp
Related Servers
Alternatives to inspect-logs-mcp
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
- AlicenseNot gradedqualityDmaintenanceProvides AI coding agents with tools to query, search, and analyze persisted HTTP request logs, enabling efficient debugging without terminal noise.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search Elasticsearch logs, retrieve log details, analyze service health, scan local codebases for APIs, and create Kibana dashboards.57 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to list, inspect, and export OpenCode AI coding sessions as HTML/JSON archives with secret redaction and token statistics.1MIT
- FlicenseAqualityCmaintenanceProvides structured access to Claude Code agent log files, allowing agents to query assistant lines and tool calls without reading raw JSONL data.2-
- FlicenseAqualityBmaintenanceAllows LLM agents to query Playwright JSON test results for run summaries and failure information.2-
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: compare_runs compares two specific runs, get_aggregate_stats provides cross-run statistics, get_eval_summary gives detailed metadata for a single run, get_sample retrieves granular sample data, list_logs enumerates available logs, and search_logs filters logs by criteria. The descriptions clearly differentiate their scopes, making misselection unlikely.
All tools follow a consistent verb_noun pattern with 'tool_' prefix (e.g., tool_compare_runs, tool_get_aggregate_stats). The verbs are descriptive and appropriate for their functions (compare, get, list, search), and the nouns precisely indicate the target resources (runs, stats, summary, sample, logs). This consistency aids predictability and usability.
With 6 tools, this server is well-scoped for inspecting evaluation logs. The count aligns with the domain's needs: listing and searching logs, retrieving summaries and samples, comparing runs, and aggregating statistics. Each tool earns its place without redundancy, covering essential operations without being overwhelming or insufficient.
The toolset provides complete coverage for log inspection: list_logs and search_logs for discovery, get_eval_summary and get_sample for detailed analysis, compare_runs for comparison, and get_aggregate_stats for cross-run insights. There are no obvious gaps; agents can navigate from discovery to deep analysis seamlessly, supporting typical evaluation workflows.