Kibana MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | Port for HTTP server | 3000 |
| LOG_LEVEL | No | Logging level (debug, info, warn, error) | info |
| KIBANA_URL | No | The URL of your Kibana instance (required) | |
| MCP_TRANSPORT | No | The transport mode for the MCP server (http or stdio) | http |
| KIBANA_API_KEY | No | Your Kibana API key for authentication | |
| KIBANA_PASSWORD | No | Your Kibana password for authentication | |
| KIBANA_USERNAME | No | Your Kibana username for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dashboardsB | List all Kibana dashboards with optional search filtering |
| get_dashboardC | Get detailed information about a specific dashboard |
| export_dashboardC | Export a dashboard with all its dependencies (visualizations, data views, etc.) |
| list_visualizationsB | List all Kibana visualizations |
| get_visualizationC | Get detailed information about a specific visualization |
| list_data_viewsB | List all data views (index patterns) in Kibana |
| search_logsC | Search Elasticsearch data through Kibana using Elasticsearch query DSL |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Kibana Dashboards | List of all available Kibana dashboards |
| Kibana Visualizations | List of all available Kibana visualizations |
| Kibana Data Views | List of all available data views (index patterns) |
| Kibana Saved Searches | List of all saved searches |
TDQS
Scored across 7 tools
Most tools have distinct purposes targeting specific Kibana resources like dashboards, visualizations, data views, and logs. However, get_dashboard and get_visualization are structurally similar (both retrieve details), which could cause minor confusion if an agent needs to differentiate between resource types without clear context. The other tools are well-separated by action and resource.
All tools follow a consistent verb_noun naming pattern using snake_case (e.g., list_dashboards, get_visualization, search_logs). The verbs (export, get, list, search) are appropriately chosen for their actions, and there are no deviations in style or convention throughout the set.
With 7 tools, this server is well-scoped for Kibana operations, covering key areas like dashboards, visualizations, data views, and log searches. Each tool serves a clear purpose without redundancy, making the count appropriate for the domain and not overwhelming for agents to navigate.
The toolset covers listing and getting resources, plus exporting dashboards and searching logs, but lacks CRUD operations for creating, updating, or deleting dashboards, visualizations, or data views. This is a notable gap that could limit agents from performing full lifecycle management, though basic retrieval and search workflows are supported.