Log MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_MCP_DIR | No | Colon-separated paths to log directories to monitor (e.g., /var/log:/tmp/logs:$XDG_RUNTIME_DIR/log) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_log_filesA | Lists all log files in $XDG_RUNTIME_DIR/log. Use this FIRST when user says 'inspect', 'inspector', 'logs', or reports errors/problems. This is the entry point for log inspection - discover available logs before using other tools. |
| get_log_contentA | Returns the content of a specific log file from $XDG_RUNTIME_DIR/log. Use this to inspect runtime logs when debugging errors or investigating problems. For large files, use read_log_paginated instead. |
| read_log_paginatedA | Reads a paginated portion of a log file. Useful for large log files. Uses token-based pagination to respect AI context limits. Tracks file modifications to detect changes between pagination calls. |
| search_log_fileA | Searches a log file using regex pattern and returns matching lines with surrounding context. Supports token-based pagination to respect AI context limits. |
| head_logA | Reads the beginning of a log file (like Unix 'head' command). Uses token-based pagination to respect AI context limits. |
| tail_logA | Reads the end of a log file (like Unix 'tail' command). Uses token-based pagination to respect AI context limits. Ideal for checking recent log entries. |
| read_log_rangeA | Reads a specific range of lines from a log file. Uses token-based pagination to respect AI context limits. |
| find_errorsA | Quickly finds error lines in a log file by matching common error patterns (ERROR, Exception, FATAL, Failed, Traceback, panic, etc.). Ideal for quick diagnostics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| runtime-logs | Information about runtime log inspection capabilities |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: listing, reading, searching, head/tail, range, and error-finding. Minor overlap exists between get_log_content and read_log_paginated, and between search_log_file and find_errors, but the descriptions provide enough guidance to disambiguate.
All tool names follow a consistent snake_case verb_noun pattern (list_log_files, get_log_content, read_log_paginated, search_log_file, head_log, tail_log, read_log_range, find_errors). The pattern is predictable and easy for an agent to infer.
8 tools is well-scoped for a log inspection server. Each tool covers a distinct log-reading need without unnecessary bloat or missing core operations.
The tool set covers the full log inspection workflow: discovering log files, reading full content, paginated reading, searching, head/tail, line ranges, and quick error detection. No obvious dead ends or critical missing operations for the stated purpose.