
Kibana Mcp
io.github.mshegolevPublished by GitHub account mshegolevv0.1.1Updated Oct 25, 2026
Kibana/Elasticsearch MCP — log search, aggregations, index discovery, dashboards.
Overview
Read-only MCP server for Kibana and Elasticsearch that lets an assistant search logs, run aggregations, list indices and browse dashboards.
- What you can do
- List indices with health, document counts and size, optionally filtered by pattern. Search logs in an index with full-text query, time range, sort order and result size. Aggregate logs by a field with count, average, sum, minimum or maximum metrics. List saved dashboards with search and pagination, and fetch one dashboard with its panel breakdown. Results come back as structured JSON and markdown text.
- When to use it
- Useful when an assistant needs to investigate logs, count errors by level or service, find which indices exist, or look up Kibana dashboards during debugging or incident review, without opening the Kibana UI.
- Requirements
- Runs locally as a Python package (pip install kibana-mcp or uvx kibana-mcp), or as a Docker image. Requires KIBANA_URL; optional ELASTICSEARCH_URL for direct Elasticsearch access, otherwise requests go through the Kibana Console proxy. Authentication uses KIBANA_API_KEY, or KIBANA_USERNAME with KIBANA_PASSWORD, or anonymous access. KIBANA_SSL_VERIFY can be set to false for self-signed certificates. Network access to the Kibana or Elasticsearch host is needed.
Installation
In SourceWeft
- Open Kibana Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
kibana-mcp
[PyPI version] [Python 3.10+] [License: MIT] [Tests]
MCP server for Kibana / Elasticsearch — log search, aggregations, index discovery, and dashboard browsing via Claude and any MCP-compatible agent.
Why another Kibana MCP?
Existing integrations require a running Kibana instance with browser-level credentials and often wrap the Kibana UI rather than the stable REST APIs. This server:
- Hits Elasticsearch REST API directly for log queries (faster, stable across Kibana UI changes)
- Falls back to the Kibana Console proxy when no direct ES URL is configured (zero extra firewall rules)
- Supports ApiKey auth (best for agents) as well as Basic auth and anonymous access
- Returns both structured JSON (
outputSchema) and markdown text so it works with any MCP client - Is read-only — all tools carry
readOnlyHint: true, no data is modified
Tools
Installation
Or run directly with uvx:
Configuration
Environment Variables
Auth priority: ApiKey > Basic > anonymous.
Copy .env.example to .env and fill in your values.
MCP Client Configuration (Claude Desktop / claude.app)
Or with direct ES access for better performance:
Docker
Usage Examples
Log Search
→ kibana_search_logs(index="logs-*", query="level:ERROR AND service:api", size=50, time_from="2026-04-18T09:00:00Z")
→ kibana_search_logs(index="nginx-*", query="status:500", sort_order="asc", size=100)
Aggregations
→ kibana_aggregate_logs(index="logs-*", group_by="level", time_from="2026-04-18T09:00:00Z")
→ kibana_aggregate_logs(index="logs-*", group_by="service.keyword", metric="avg", metric_field="response_time_ms")
Index Discovery
→ kibana_list_indices()
→ kibana_list_indices(pattern="filebeat-*")
Dashboards
→ kibana_list_dashboards(search="infrastructure")
→ kibana_get_dashboard(dashboard_id="<id from list_dashboards>")
Performance Characteristics
- Log search (
kibana_search_logs): typically 50-500ms with direct ES URL; add 100-200ms when routing through Kibana Console proxy - Aggregations (
kibana_aggregate_logs):size:0queries — no hits transferred, usually 10-100ms - Index listing: single
_cat/indicescall, O(index_count) response, typically <100ms - Dashboard APIs: Kibana Saved Objects API, typically 50-200ms; latency is Kibana-side, not network
- Set
ELASTICSEARCH_URLdirectly if your agent does frequent log searches — eliminates the proxy overhead
Development
License
MIT — see LICENSE.
Source: README.md at commit b1c596c
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts