Kibana Bridge MCP
Related Servers
Alternatives to Kibana Bridge MCP
No user-submitted related servers found.
Related Servers
- 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.719 npm3MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search Elasticsearch logs, retrieve log details, analyze service health, scan local codebases for APIs, and create Kibana dashboards.519 npmMIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables querying Elasticsearch logs from AI assistants using natural language, with optional SSH tunnel support.-
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- FlicenseAqualityCmaintenanceEnables searching and analyzing Kibana logs through Dev Tools console proxy using only Kibana credentials, with tools for overviews, patterns, anomaly explanations, traces, and query DSL access.14-
- AlicenseAqualityAmaintenanceEnables AI agents to search and analyze SAP Commerce Cloud (CCv2) runtime logs via OpenSearch Dashboards using a session cookie, providing read-only tools for full-text search and error aggregation.3MIT
TDQS
Scored across 5 tools
Each tool targets a distinct stage of log investigation: summarize_logs returns summary statistics only, search_logs returns matching hits, get_log_context returns surrounding entries, inspect_log returns full metadata for one entry, and available_log_fields returns schema information. There is little to no functional overlap.
Most names follow a snake_case verb_noun pattern (search_logs, get_log_context, inspect_log, summarize_logs), but available_log_fields starts with an adjective/noun rather than a verb, which is a minor inconsistency.
Five tools cleanly cover schema discovery, high-level summary, targeted search, contextual viewing, and single-document inspection without redundancy. This is a well-scoped set for the server's purpose.
For a read-only log investigation bridge, the tools cover the full Discover-style workflow: learn fields, summarize data shape, search with filters, inspect surrounding context, and drill into a single entry. No obvious missing read operations for the domain.