Skip to main content
Glama
ivan23kor

logpiper-mcp

by ivan23kor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to logpiper-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • log-mcp-server

      sheikhBasit
      F
      license
      B
      quality
      D
      maintenance
      A log analysis MCP server that enables tailing, searching, filtering, and summarizing logs from local files and Docker containers.
      7
      -

    • 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

    • console-mcp

      rohithgoud30
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for streaming and searching macOS Console.app and iOS device logs, enabling real-time log access and debugging through natural language.
      14
      2 npm
      2
      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.3/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have clearly distinct roles, but get_new_logs and get_logs_paginated both retrieve logs and could be confused by an agent skimming descriptions. The streaming vs. pagination distinction is present but requires careful reading.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_, list_, search_, cleanup_), with no mixed conventions or vague verbs. The naming is predictable and easy to extrapolate.

    Tool Count5/5

    Five tools is a well-scoped size for a log management server, covering retrieval, search, session listing, and cleanup without unnecessary bloat or feeling thin.

    Completeness3/5

    The read and lifecycle side is reasonably covered with search, pagination, streaming, and cleanup, but there is no ingestion or write capability for logs/sessions. This is a notable gap if the server is meant to manage logs end-to-end.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources