Skip to main content
Glama
purelledhand

MCP Error Relay

by purelledhand

Related Servers

Alternatives to MCP Error Relay

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to search and analyze Elasticsearch logs for errors, detect recurring patterns, analyze error-rate trends, and retrieve full trace context through MCP tools.
      6
      MIT
    • 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.
      10 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Runtime feedback MCP server for AI coding agents. It watches dev server logs, parses errors, and exposes them as MCP tools so AI agents can instantly verify code changes.
      30 npm
      3
      AGPL 3.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides coding agents with compressed failure context via MCP, reducing the need to parse full raw logs.
      1
      -
    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that exposes tools to query Datadog monitors and logs, and AWS CloudWatch Logs, and to group recurring errors by fingerprint. Designed for use with Claude Code to diagnose issues and propose fixes.
      MIT

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing servers, fetching recent errors, and analyzing a specific error. There is no overlap; the tools are complementary stages of a single diagnostic workflow.

    Naming Consistency5/5

    All tool names follow the same 'get_' + noun pattern in snake_case (get_recent_errors, get_error_details, get_server_list). The naming is perfectly consistent and predictable.

    Tool Count5/5

    Three tools is well-scoped for an error relay server. Each tool earns its place, covering discovery, retrieval, and analysis without any redundancy.

    Completeness5/5

    The tool set covers the full error-diagnosis workflow: discover available servers, retrieve error logs, and get root-cause analysis with actionable fixes. There are no obvious gaps or dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues