Skip to main content
Glama
sheikhBasit

log-mcp-server

by sheikhBasit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to log-mcp-server

No user-submitted related servers found.

    Related Servers

    • Log Analyzer MCP Server

      suriya-ML
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for intelligent log analysis providing semantic search, error pattern clustering, and smart error detection. It enables users to process, vectorize, and query local logs to efficiently identify issues and generate AI-powered summaries.
      MIT

    • log-mcp

      ascii766164696D
      A
      license
      A
      quality
      D
      maintenance
      MCP server for log file analysis. Gives LLMs the ability to efficiently analyze large log files without loading them into context.
      7
      100
      MIT

    • log-collector

      bonsai
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for collecting and analyzing CLI/web server error logs. Enables watching log files/directories, parsing common error patterns, and querying/analyzing logs through natural language.
      3 npm
      MIT

    • loki-tail-mcp

      snickery
      A
      license
      A
      quality
      B
      maintenance
      An MCP server for Grafana Loki that enables LLMs to query, tail, and analyze logs, featuring fuzzy container-name matching, compact output, and tools for log patterns, volume, and label discovery. It can run as a local stdio server or a containerized HTTP service.
      9
      MIT

    • MCP Container Tools

      simseksem
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for managing and monitoring Docker, Docker Compose, and Kubernetes environments alongside Azure Application Insights. It enables advanced log filtering, container lifecycle management, and querying of cloud application traces and metrics.
      7
      MIT
    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

    B3.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct source (Docker container vs. log file) and operation (tail, search, filter, summarize). Even within groups, actions are clearly differentiated. No two tools appear to do the same thing.

    Naming Consistency2/5

    Docker tools follow a 'docker_<noun>' pattern, while file tools use bare verbs (search, tail) or verb_noun (filter_level). This inconsistency disrupts a predictable naming convention.

    Tool Count5/5

    Seven tools is appropriate for log management: covering tail, search, filter, and summary for both Docker and file logs. Not too many to overwhelm, not too few to be insufficient.

    Completeness4/5

    Covers essential log operations like tailing, searching, filtering, and error grouping. Minor gaps exist, such as live tailing or listing available log files, but the core workflow is well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources