Log Analyzer MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_LOG_FILE | No | Optional path to a log file for MCP server logs | |
| MCP_LOG_LEVEL | No | Logging level for the MCP server (e.g., INFO, DEBUG, WARNING, ERROR) | INFO |
| LOG_DIRECTORIES | No | JSON array of directories containing log files to analyze (e.g., '["/path/to/your/app/logs"]') | |
| PYTHONIOENCODING | No | Set Python I/O encoding | utf-8 |
| PYTHONUNBUFFERED | No | Set to '1' to ensure Python output is not buffered | 1 |
| LOG_PATTERNS_ERROR | No | JSON array of regex patterns to identify error log entries (e.g., '["Exception:.*"]') | |
| LOG_CONTEXT_LINES_AFTER | No | Number of lines to include after a matched log entry for context | |
| LOG_CONTEXT_LINES_BEFORE | No | Number of lines to include before a matched log entry for context |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_tests | Analyze the most recent test run and provide detailed information about failures. Args: summary_only: Whether to return only a summary of the test results |
| run_tests_no_verbosity | Run all tests with minimal output (verbosity level 0). |
| run_tests_verbose | Run all tests with verbose output (verbosity level 1). |
| run_tests_very_verbose | Run all tests with very verbose output (verbosity level 2). |
| ping | Check if the MCP server is alive. |
| create_coverage_report | Run the coverage report script and generate HTML and XML reports. Args: force_rebuild: Whether to force rebuilding the report even if it exists Returns: Dictionary containing execution results and report paths |
| run_unit_test | Run tests for a specific agent only. This tool runs tests that match the agent's patterns including both main agent tests and healthcheck tests, significantly reducing test execution time compared to running all tests. Use this tool when you need to focus on testing a specific agent component. Args: agent: The agent to run tests for (e.g., 'qa_agent', 'backlog_agent') verbosity: Verbosity level (0=minimal, 1=normal, 2=detailed), default is 1 Returns: Dictionary containing test results and analysis |
| search_log_all_records | Search for all log records, optionally filtering by scope and content patterns, with context. |
| search_log_time_based | Search logs within a time window, optionally filtering, with context. |
| search_log_first_n_records | Search for the first N (oldest) records, optionally filtering, with context. |
| search_log_last_n_records | Search for the last N (newest) records, optionally filtering, with context. |
| get_server_env_details | Returns sys.path and sys.executable from the running MCP server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Darkstar326/log_analyzer_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server