Kibana MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIBANA_URL | Yes | Kibana server address (e.g. http://localhost:5601) | |
| KIBANA_CA_CERT | No | CA certificate path (optional, for SSL verification) | |
| KIBANA_TIMEOUT | No | Request timeout in ms | 30000 |
| KIBANA_PASSWORD | Yes | Kibana password | |
| KIBANA_USERNAME | Yes | Kibana username | |
| KIBANA_MAX_RETRIES | No | Max request retries | 3 |
| KIBANA_DEFAULT_SPACE | No | Default Kibana space | default |
| NODE_TLS_REJECT_UNAUTHORIZED | No | Set to 0 to disable SSL certificate validation (use with caution) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusB | Get Kibana server status with multi-space support |
| execute_kb_apiC | Execute a custom API request for Kibana with multi-space support |
| search_kibana_api_pathsC | Search Kibana API endpoints by keyword |
| list_all_kibana_api_pathsB | List all Kibana API endpoints as a resource list |
| get_kibana_api_detailC | Get details for a specific Kibana API endpoint |
| get_available_spacesC | Get all available Kibana spaces with current context |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| kibana-tool-expert | |
| kibana-resource-helper |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| kibana-api-paths | |
| kibana-api-path-detail |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: execute_kb_api performs custom API calls, get_available_spaces lists spaces, get_kibana_api_detail provides endpoint details, get_status checks server status, list_all_kibana_api_paths enumerates all endpoints, and search_kibana_api_paths searches endpoints. The descriptions reinforce these unique functions, making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case: execute_kb_api, get_available_spaces, get_kibana_api_detail, get_status, list_all_kibana_api_paths, and search_kibana_api_paths. The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 6 tools, the count is well-scoped for a Kibana MCP server focused on API exploration and execution. Each tool earns its place by covering distinct aspects like status, spaces, endpoint listing, searching, detailing, and execution, avoiding bloat while providing comprehensive functionality.
The tool set is highly complete for exploring and interacting with Kibana APIs, covering discovery (list/search), details, spaces, status, and execution. A minor gap exists in lacking direct CRUD operations for Kibana objects like dashboards or visualizations, but agents can work around this using execute_kb_api for custom requests.