Skip to main content
Glama
ePotok22

kibana-console-mcp

by ePotok22

Related Servers

Alternatives to kibana-console-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only querying and analysis of Kibana logs through a logged-in sid Cookie, including keyword/time/index searches, traceId lookups, surrounding log context, and aggregations by service, level, or host. It also validates Kibana connection status and redacts sensitive fields such as cookies, tokens, and passwords.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search, summarize, and inspect Kibana/OpenSearch Dashboards logs through the user's logged-in browser session, eliminating the need for API keys or service accounts.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables querying and searching logs from Kibana (ELK stack) via MCP, with support for project-based data views, trace ID correlation, and log expansion.
      -
    • 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
      17 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides seamless access to Kibana and Periscope logs through a unified API with KQL and SQL querying, AI-powered log analysis, and support for searching across 1.3+ billion logs in 9 indexes.
      1
      -

    TDQS

    A4.2/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: querying (es_search, es_count, es_esql), discovery (es_list_indices, es_get_mappings, kbn_list_data_views), investigation (es_trace, es_find, es_patterns, es_why, es_overview), and administrative access (kbn_status, kbn_find_saved_objects, es_request). Overlapping-looking tools like es_find vs es_search are explicitly differentiated by purpose and guidance in their descriptions.

    Naming Consistency4/5

    The set follows a mostly consistent convention: es_ for Elasticsearch operations and kbn_ for Kibana operations, with verb_noun pairs like es_get_mappings, es_list_indices, kbn_find_saved_objects. A few tools use noun/adverb style names (es_patterns, es_why, es_overview), which breaks the verb-led pattern but remains predictable and readable.

    Tool Count5/5

    14 tools is well-scoped for a Kibana/Elasticsearch investigation console. Each tool covers a distinct capability — from low-level search, to aggregations, to incident-analysis helpers, to saved-object access — without feeling bloated or redundant.

    Completeness5/5

    The tool surface is comprehensive for its read-only investigation purpose: it covers index discovery, field mappings, query execution (DSL, count, ES|QL), log pattern analysis, trace following, statistical comparisons, overview generation, saved object lookup, and a general escape hatch for unlisted Elasticsearch APIs. No obvious dead ends remain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues