mcp-syslog
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| syslog_sources_toolA | List log sources available to query, with size and last-write time. |
| syslog_search_toolC | Search collected logs by source, time window, severity and pattern. |
| syslog_grep_toolC | Regex search across all sources, or within one named source. |
| syslog_tail_toolB | Return the most recent entries for one source. |
| syslog_context_toolA | Return log entries surrounding a specific moment. Use this after an alert names a time. Omitting source spans the whole fleet, which is how a failure gets correlated with whatever else was happening. |
| syslog_stats_toolA | Summarise log volume and error rate per source. |
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 distinct purpose: listing sources, regex search, structured search, tailing recent entries, context around a time, and statistics. Although grep and search both query logs, their descriptions differentiate them (regex vs. structured filters), so an agent can select the right one without confusion.
All tools follow the same pattern: 'syslog_' + verb/noun + '_tool'. The naming is consistent in style (snake_case) and structure, making it predictable and easy to infer functionality from the name.
6 tools is a well-scoped set for a syslog query server. Each tool serves a clear operational need without redundancy, and the count is within the ideal range for a focused MCP server.
The tool surface covers the core lifecycle of log querying: discovering sources, searching (both simple and advanced), tailing, contextual analysis, and statistics. No obvious gaps like missing CRUD operations (not applicable here) or missing workflow steps are evident.