Skip to main content
Glama
fasterv410

logflare-mcp

by fasterv410
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to logflare-mcp

No user-submitted related servers found.

    Related Servers

    • Sumo Logic MCP Server

      vinit-devops
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Sumo Logic's REST APIs through MCP, allowing log search, dashboard management, metrics querying, collector and monitor operations.
      5
      MIT

    • papertrail-mcp

      andreimaxim
      F
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for searching migrated Papertrail logs via SolarWinds Observability API. Provides tools to list environments and perform bearer-authenticated log queries through stdio.
      2
      33 npm
      -

    • InfluxDB MCP Server

      Quorralyne
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with InfluxDB v3 (Core/Enterprise/Cloud Dedicated) through MCP clients. Supports database management, data querying and writing, schema inspection, and token administration operations.
      243 npm
      MIT

    • mcplogview

      skromesch
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes configured log files as MCP tools, enabling agents to list, query, and follow logs from local and SSH sources.
      MIT

    • humio-mcp

      weihong-xu-hpe
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Humio/LogScale dashboards and executing search queries via MCP, with multi-cluster support and configurable time ranges.
      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

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct operation: ad-hoc queries, saved endpoint execution, source retrieval, schema inspection, recent events, and listing. No two tools have overlapping purposes; descriptions clearly differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., execute_query, list_sources). The prefixes 'get', 'list', 'execute', and 'query' are uniformly used for similar actions.

    Tool Count5/5

    With 7 tools, the server is well-scoped for a logging/query domain. Each tool serves a clear purpose without redundancy, and the count is neither too sparse nor overwhelming.

    Completeness4/5

    The tool set covers core operations: listing and inspecting sources, querying via ad-hoc SQL or saved endpoints, and fetching recent events. Missing create/update/delete for sources and endpoints, but these may be out of scope for a read-focused MCP server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources