Local Logs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGS_DIR | No | Directory containing log files. If not specified, the server automatically searches for logs in priority order: ./logs, ./apps/backend/logs, ./server/logs, ./backend/logs, /var/log (Linux/Mac), C:\logs (Windows) | |
| LOG_EXTENSIONS | No | Comma-separated log file extensions | .log,.txt |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_log_filesB | Get list of available log files with metadata |
| tail_logA | Get the last N lines from a log file |
| get_errorsC | Get recent error log entries |
| get_server_statusB | Get server status summary from logs |
| watch_logC | Monitor a log file for changes |
| search_logsC | Search for specific text in log files |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.