Skip to main content
Glama
nrapendra-singh

Log Pruner MCP Server

by nrapendra-singh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Log Pruner MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • token-filter-mcp

      VMexicano
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that intelligently filters and compresses tool outputs to reduce context window usage, saving up to 90% of tokens by removing noise such as passing tests and redundant information.
      5
      36 npm
      MIT

    • cctx-mcp

      nikondrat
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides structure-aware code analysis (symbol trees, dependencies, docs) to reduce AI agent token consumption by up to 99%, along with Git commit intelligence.
      MIT

    • smart-context-mcp

      Arrayo
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that reduces AI agent token usage by up to 90% through intelligent context compression. Enables efficient code exploration, multi-file refactoring, and debugging by providing tools for smart reading, searching, and managing code context.
      4
      MIT

    • Log Analyzer MCP

      djm81
      F
      license
      B
      quality
      D
      maintenance
      A Python-based MCP server that enables AI-assisted log file analysis with features for filtering, parsing, and interpreting log outputs, plus executing and analyzing test runs with varying verbosity levels.
      12
      12
      -
    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

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct purpose: get_context retrieves logs around a timestamp, get_errors filters errors, query_logs queries OpenSearch directly, read_logs reads from a file, and summarize_logs aggregates. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: get_context, get_errors, query_logs, read_logs, summarize_logs. The naming is predictable and clear.

    Tool Count5/5

    With 5 tools, the server is well-scoped for log analysis. Each tool covers a specific operation (read, query, error extraction, context, summary) without redundancy or excessive complexity.

    Completeness5/5

    The tool set covers all essential log analysis operations: reading, querying, error inspection, context retrieval, and summarization. No obvious gaps for the intended domain of log troubleshooting.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources