mcp-for-kibana
Related Servers
Alternatives to mcp-for-kibana
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseBqualityDmaintenanceEnables 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.717 npm3MIT
- AlicenseAqualityBmaintenanceEnables LLM clients to interact with OpenSearch Dashboards, including reading saved objects, listing tenants and index patterns, and querying logs through the Dashboards API.5MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search Elasticsearch logs, retrieve log details, analyze service health, scan local codebases for APIs, and create Kibana dashboards.517 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Kibana security alerts, rules, and exception lists via the Model Context Protocol.13MIT
- AlicenseBqualityDmaintenanceEnables interaction with Elasticsearch clusters for health checks, index management, document CRUD operations, and search via natural language.1011 npmMIT
TDQS
Scored across 16 tools
Each tool targets a distinct resource and action: dashboards, panels, data views, saved objects, and short URLs are cleanly separated, and the ES|QL panel variants are distinguished by panel type. Where overlap could exist (add_panel vs the ES|QL-specific panel tools), the descriptions explicitly clarify when to use which.
All tool names follow a consistent snake_case verb_noun pattern: search_dashboards, create_dashboard, add_panel, list_data_views, resolve_short_url, etc. The verb prefixes are uniform and predictable, making the tool set easy to navigate.
16 tools is slightly above the ideal 3-15 range, but the breadth is justified by the multiple Kibana subsystems covered: dashboards, visualizations, data views, saved objects, and short URLs. Each tool has a clear role, so the count feels reasonable rather than bloated.
The core dashboard-building workflow is well covered, including create/read/update, panel management, data-view discovery, and saved-object transfer. However, there are notable gaps: no delete operations for dashboards, data views, visualizations, or short URLs, and no way to remove a panel from a dashboard.