Skip to main content
Glama
sid-s-s

Kibana Log Analysis & API Dashboard MCP Server

by sid-s-s
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Kibana Log Analysis & API Dashboard MCP Server

No user-submitted related servers found.

    Related Servers

    • Kibana MCP Server

      jerrelblankenship
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with Kibana dashboards, visualizations, and Elasticsearch data through read-only resources and executable tools for searching logs, exporting dashboards, and querying data.
      7
      10 npm
      3
      MIT

    • elasticsearch-mcp

      bpamiri
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to search, analyze, and interact with Elasticsearch through natural language.
      18
      Apache 2.0

    • es-error-lens

      TerraCo89
      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

    • es-mcp

      artisan-soohao
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables querying Elasticsearch logs from AI assistants using natural language, with optional SSH tunnel support.
      -

    • elastic_mcp

      ahmednaguib
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI clients to search and retrieve Elasticsearch application logs through a provided search tool.
      Apache 2.0
    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 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: searching logs, retrieving details, analyzing health, scanning APIs, and creating dashboards. No overlap between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_logs, get_log_details), making them predictable and easy to distinguish.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its dual focus on log analysis and API dashboard creation, without being too sparse or overloaded.

    Completeness4/5

    Core workflows are covered (search, details, health analysis, API discovery, dashboard creation), but minor gaps exist—e.g., missing tools for listing, updating, or deleting dashboards.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources