Skip to main content
Glama
ahmad2x4

Seq MCP Server

by ahmad2x4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Seq MCP Server

No user-submitted related servers found.

    Related Servers

    • Seq MCP Server

      lancer1977
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for querying structured logs from Datalust Seq, providing tools to search logs, retrieve recent errors, fetch events, and check health.
      MIT

    • mcp-sumologic

      giftHEALTH
      F
      license
      B
      quality
      B
      maintenance
      MCP server that integrates with Sumo Logic's API to perform log searches, data discovery, metrics queries, and monitoring.
      15
      7 npm
      -

    • Logpoint MCP Server

      Aashish079
      F
      license
      Not graded
      quality
      B
      maintenance
      Logpoint MCP Server provides MCP endpoints for Logpoint SIEM, enabling search, incident management, alert rules, and integrations with n8n and Claude for SIEM operations.
      -

    • Overwatch MCP

      malindarathnayake
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables querying logs and metrics from Graylog, Prometheus, and InfluxDB 2.x. It provides tools for executing Lucene log searches, PromQL queries, and Flux queries directly within MCP-compatible clients.
      MIT

    • Mezmo MCP Server

      riefer02
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for retrieving and filtering logs from Mezmo with a quota-conscious design and intelligent defaults. It enables users to discover and query logs by application, level, and custom time ranges to streamline debugging while minimizing API usage.
      1
      -
    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

    D1.9/5.0

    Scored across 3 tools

    Disambiguation3/5

    The tools appear to target different aspects of a Seq server (alert state, events, signals), but with only one description available for 'get-events', it's unclear how 'get-alertstate' and 'get-signals' differ in purpose. This creates some ambiguity, though the distinct names suggest separate functions.

    Naming Consistency5/5

    All three tools follow a consistent 'get-[noun]' naming pattern using kebab-case, which is predictable and readable. There are no deviations in style or verb usage across the tool set.

    Tool Count2/5

    With only 3 tools, this server feels under-scoped for a logging/monitoring domain like Seq, which typically involves more operations such as creating alerts, filtering logs, or managing signals. The count is too low to cover the apparent scope effectively.

    Completeness2/5

    The tool set is severely incomplete for a Seq server, lacking essential operations like creating or updating alerts, sending logs, or configuring signals. Only read-only 'get' operations are provided, which will limit agents to passive monitoring without the ability to interact or modify the system.

    Maintenance

    ActivityStale
    ResponsivenessWithin a week

    Resources