Skip to main content
Glama
Sign In
mcp-for-kibana

mcp-for-kibana

by pedro-angel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-for-kibana

No user-submitted related servers found.

    Related Servers

    • Kibana Dashboard Builder

      brienhackney
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to create and manage Kibana dashboards, Lens visualizations, and data views via the Kibana Saved Objects API. It allows for programmatically listing existing resources and assembling new visualizations into dashboards through natural language commands.
      -

    • 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
      28 npm
      3
      MIT

    • opensearch-dashboard-mcp

      danilin-em
      A
      license
      A
      quality
      D
      maintenance
      Enables LLM clients to interact with OpenSearch Dashboards, including reading saved objects, listing tenants and index patterns, and querying logs through the Dashboards API.
      5
      MIT

    • kibana-mcp

      ggilligan12
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Kibana security alerts, rules, and exception lists via the Model Context Protocol.
      13
      MIT

    • Elasticsearch MCP Server

      jesee
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Elasticsearch clusters for health checks, index management, document CRUD operations, and search via natural language.
      10
      7 npm
      MIT
    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 21 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but add_panel and add_library_panel overlap (both add a visualization to a dashboard), and the three add_esql_*_panel tools could be seen as variants of one operation. Their descriptions do help clarify the intended use cases.

    Naming Consistency5/5

    All tools use snake_case with a predictable verb_noun pattern (add_*, create_*, update_*, get_*, search_*, list_*, describe_*, export_*, import_*, resolve_*). There are no mixed conventions or inconsistent verb styles.

    Tool Count3/5

    21 tools is heavy for this surface; the three ES|QL panel tools and separate export/import saved-object tools add niche operations that could be consolidated. While each tool has a purpose, the set is over-segmented relative to typical scoped MCP servers.

    Completeness3/5

    Core create/read/update workflows exist for dashboards, visualizations, data views, and panels, but deletion is entirely absent (no delete_dashboard, delete_visualization, delete_data_view, delete_panel, delete_saved_objects). There is also no explicit update_dashboard by id, leaving lifecycle gaps.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources