Manage Kibana spaces, APIs, and saved objects from MCP-compatible clients using API discovery and multiple authentication methods.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Kibana.
The Kibana MCP server gives MCP clients access to a Kibana instance through natural-language requests or direct tool calls. It covers server status, space listing, API endpoint discovery, custom Kibana API requests, and saved-object management. Supported saved-object types include dashboards, visualizations, index patterns, searches, configuration objects, Lens objects, maps, tags, Canvas workpads, and Canvas elements.
The server also includes analysis operations for saved objects. Agents can inspect object dependencies, assess the impact of a deletion, check an individual dashboard's health, or scan all dashboards for health issues. The project is community-maintained and is not an official Elastic or MCP product.
The Kibana MCP server builds its API discovery behavior from the official Kibana OpenAPI YAML specification for Elastic Stack 8.x. Clients can search available API paths, list all paths, or retrieve details for a particular method and encoded path. The execute_kb_api tool then provides a way to issue custom Kibana API requests.
It supports two MCP transport modes. Stdio is the default for local clients, while HTTP mode exposes an MCP endpoint and a health-check endpoint for remote access. HTTP mode generates UUID-based sessions automatically. Requests can target a configured default Kibana space, and saved-object operations include pagination, bulk updates or deletions, references, and optimistic concurrency controls.
Install the npm package globally or run it directly with npx. Node.js 18 or newer is required. Set KIBANA_URL to the address of the Kibana server and provide one authentication method: KIBANA_API_KEY, KIBANA_USERNAME with KIBANA_PASSWORD, or KIBANA_COOKIES.
Optional settings include KIBANA_DEFAULT_SPACE, KIBANA_CA_CERT, KIBANA_TIMEOUT, MCP_TRANSPORT, MCP_HTTP_PORT, and MCP_HTTP_HOST. NODE_TLS_REJECT_UNAUTHORIZED can disable TLS certificate validation, but the project notes that this should be used cautiously. In HTTP mode, the MCP endpoint is available at /mcp, with /health available for health checks.
The Kibana MCP server provides tools for:
It also exposes resources for the complete API path list, keyword-based path searches, and individual endpoint details.
The README describes the implementation as based on Kibana's Elastic Stack 8.x API specification, so API behavior may depend on the connected Kibana version. Successful operations also depend on the permissions granted to the selected authentication method. SSL certificate problems may require a configured CA certificate or a deliberate TLS validation change. The companion Elasticsearch MCP server mentioned by the project is a separate server for direct Elasticsearch data operations; it is not included here.
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/kibana)<a href="https://allmcps.com/mcp/kibana"><img src="https://allmcps.com/api/badge/kibana?style=directory" alt="Kibana on AllMCPs" /></a>