Skip to main content
Glama
crunchtools

mcp-syslog

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-syslog

No user-submitted related servers found.

    Related Servers

    • AI Incident Monitoring RCA MCP

      lokeshkundi15
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides telemetry tools for retrieving recent logs and system metrics to support root-cause analysis of infrastructure incidents. Enables autonomous incident triage with grounded verification and human-in-the-loop remediation.
      1
      -

    • LogLens

      Suteerth03
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables log analysis through MCP tools for searching logs, retrieving error contexts, and summarizing incidents with self-verified root-cause hypotheses.
      6 npm
      MIT

    • Multi-Container Log Correlator

      parajiholkar
      F
      license
      A
      quality
      C
      maintenance
      Enables debugging of distributed transactions by continuously ingesting Docker container logs, indexing them by trace/request ID, and exposing MCP tools to search, tail, and correlate logs across services.
      7
      -

    • cortex

      dinglebear-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language querying and investigation of homelab logs from syslog, Docker, OTLP, and AI transcripts, with SQLite full-text search, timeline correlation, incident clustering, and fleet topology insights.
      3
      AGPL 3.0

    • Log Analyzer MCP Server

      adai78
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying and analyzing logs from multiple remote Unix hosts via the Log Collector API, with tools for search, error detection, and summary generation.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources