
Kibana
io.github.TocharianOU由 GitHub 帳號 TocharianOU 發布v0.11.1更新於 Nov 22, 2026
Kibana MCP Server with dynamic API discovery and comprehensive Elastic Stack integration
概覽
把助理連接到 Kibana 執行個體,用來搜尋 Elasticsearch 日誌與資料、管理儀表板等已儲存物件,並瀏覽 Kibana API。
- 可以做什麼
- 查看 Kibana 狀態並列出可用的空間
- 以 Query DSL 搜尋 Elasticsearch 文件、日誌與聚合,範圍受使用者索引權限限制
- 搜尋、讀取、建立、更新已儲存物件,並批次更新或刪除儀表板、視覺化、索引樣式、標籤等
- 分析已儲存物件的相依關係、刪除影響與儀表板健康狀態,支援批次掃描
- 瀏覽、搜尋並檢視 Kibana API 端點,並執行自訂 Kibana API 請求
- 適用情境
- 適合讓助理在既有 Kibana 部署中追查日誌或追蹤資料、執行聚合統計,或維護儀表板與視覺化,而不必切換到 Kibana 介面。也適合在呼叫前先了解有哪些 Kibana API 可用。
- 執行需求
- 以 npm 套件形式在本機執行(需 Node.js 18 以上),透過 stdio 通訊;也可用 MCP_TRANSPORT 與 MCP_HTTP_PORT 啟用 HTTP 模式。需要 KIBANA_URL 以及一種驗證方式:KIBANA_API_KEY、KIBANA_USERNAME 搭配 KIBANA_PASSWORD,或工作階段 Cookie。選用設定包括預設空間、CA 憑證、代理與逾時。需要能連線到 Kibana 執行個體的網路。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Kibana,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
[MseeP.ai Security Assessment Badge]
Kibana MCP Server
[npm version] [Downloads] [Ask DeepWiki]
A Kibana MCP server implementation that allows any MCP-compatible client (such as Claude Desktop) to access your Kibana instance via natural language or programmatic requests.
This project is based on the official Elastic Kibana API documentation and uses the OpenAPI YAML specification from Elastic Stack 8.x. For details, see the Kibana API documentation.
This project is community-maintained and is not an official product of Elastic or MCP.
💡 Companion Project: For complete Elastic Stack integration, pair this with Elasticsearch MCP Server for direct Elasticsearch data operations.
🚀 Installation
From Source
🎯 Quick Start
Claude Desktop Integration (Recommended)
Add to your Claude Desktop configuration file:
- MacOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Direct CLI Usage
HTTP Mode (Remote Access)
Access at: http://localhost:3000/mcp
Health check: http://localhost:3000/health
Securing HTTP mode. Every session on /mcp acts with the Kibana credentials the server was started with, so treat the endpoint as sensitive:
- By default the server listens on
localhostonly and rejects requests whoseHostheader is not a loopback name (DNS rebinding protection). - To accept remote clients, set
MCP_BEARER_TOKEN. Clients must then sendAuthorization: Bearer <token>on every/mcprequest./healthstays open. - Binding to a non-loopback address (
MCP_HTTP_HOST=0.0.0.0) withoutMCP_BEARER_TOKENlogs a warning at startup: anyone who can reach the port can use your Kibana credentials. - Behind a reverse proxy that forwards its public
Hostheader to a localhost-bound server, list that hostname inMCP_ALLOWED_HOSTS.
✨ Features
Core Capabilities
- Dual transport modes: Stdio (local) and HTTP (remote access)
- Multiple authentication methods: API Key, Basic Auth, Cookie-based
- Multi-space support: Enterprise-ready Kibana space management
- SSL/TLS support: Custom CA certificate configuration
- Session management: Automatic UUID generation for HTTP mode
- Dynamic API discovery: Based on official Kibana OpenAPI specification
Saved Objects Management
- Complete CRUD operations for all Kibana saved object types
- Intelligent search with pagination support
- Bulk operations for efficient mass updates
- Version control with optimistic concurrency
- Reference management for object relationships
🔧 Configuration
Required Variables
Authentication (choose one method)
Optional Variables
Proxy
Set KIBANA_PROXY when Kibana is only reachable through a proxy, for example a bastion host with an SSH dynamic port forward:
- Supported schemes:
http://,https://,socks5://andsocks5h://. Credentials can be part of the URL (socks5h://<user>:<password>@<host>:<port>). - Use
socks5hwhen the Kibana host name only resolves on the proxy side; withsocks5it is resolved locally. KIBANA_CA_CERTstill applies to the TLS connection to Kibana.- With an
https://proxy,KIBANA_CA_CERTis also used to verify the proxy's own certificate. If the proxy's certificate is issued by a different CA, put both CA certificates in the same file. KIBANA_PROXYtakes precedence overHTTP_PROXY,HTTPS_PROXYandNO_PROXY. Without it, HTTP(S) proxies from those variables keep working as before; they do not support SOCKS.
🛠️ Available Tools
Base Tools
get_status- Get Kibana server statusexecute_kb_api- Execute custom Kibana API requestssearch_elasticsearch- Search Elasticsearch documents and logs through Kibana's search API, within the user's Elasticsearch index privilegesget_available_spaces- List available Kibana spacessearch_kibana_api_paths- Search API endpointslist_all_kibana_api_paths- List all API endpointsget_kibana_api_detail- Get API endpoint details
Saved Objects Tools
vl_search_saved_objects- Search saved objects (universal)vl_get_saved_object- Get single saved objectvl_create_saved_object- Create new saved objectvl_update_saved_object- Update single saved objectvl_bulk_update_saved_objects- Bulk update operationsvl_bulk_delete_saved_objects- Bulk delete operations
Supported Object Types: dashboard, visualization, index-pattern, search, config, lens, map, tag, canvas-workpad, canvas-element
Analysis Tools (v0.6.0+)
analyze_object_dependencies- Analyze saved object dependenciesanalyze_deletion_impact- Check impact before deletioncheck_dashboard_health- Dashboard health checkscan_all_dashboards_health- Batch health scanning
Elasticsearch Data Search
Use search_elasticsearch when you need to search documents, application logs, traces, or aggregations in Elasticsearch. It sends Query DSL through Kibana's /internal/search/es route instead of the Dev Tools Console proxy.
The tool is read-only and does not widen data access: Elasticsearch enforces the configured user's index privileges on every search, exactly as it does for Discover and dashboards. Indices the user cannot read return no results.
It exists because the Dev Tools Console proxy (/api/console/proxy) is gated by a separate Kibana privilege, since the Console can call any Elasticsearch API including write and admin endpoints. A user who can read the target indices but has no Dev Tools privilege gets 403 from the Console proxy; this tool gives that user search, and nothing more. If your Kibana administrators rely on withholding Dev Tools to block ad-hoc queries from an account, be aware that this tool allows Query DSL searches for it.
Example tool arguments for a bounded log search:
For high-volume logs, start with a small time window and a small size. After finding a trace or correlation id, use that value in a second narrow search instead of repeatedly scanning a broad time range. Use _source to keep only fields needed for the current investigation.
The tool rejects wildcard-only index segments such as *, **, or _all (including inside comma-separated index expressions), an empty search body, and body.size above 100. String size values are coerced and validated as numbers. The endpoint is an internal Kibana API, so compatibility should be verified after major Kibana upgrades.
📖 Resources
💬 Example Queries
Basic Operations
- "What is the status of my Kibana server?"
- "List all available Kibana spaces"
- "Show me all API endpoints related to dashboards"
Elasticsearch & Logs
- "Search the production logs for errors from service X in the last hour"
- "Find this trace id and show the surrounding log events in chronological order"
- "Search index application-logs-* using this Elasticsearch Query DSL"
- "Aggregate error counts by service for this time range"
Saved Objects
- "Search for all dashboards"
- "Find visualizations containing 'nginx' in the title"
- "Create a new dashboard named 'Sales Overview'"
- "Update the description of dashboard 'my-dashboard-123'"
- "Delete multiple dashboards by their IDs"
Health & Analysis
- "Check health of dashboard 'overview'"
- "Analyze dependencies for visualization 'viz-123'"
- "Scan all dashboards for health issues"
🐛 Troubleshooting
Connection Issues
- Verify Kibana URL is accessible
- Check authentication credentials
- For SSL issues:
NODE_TLS_REJECT_UNAUTHORIZED=0(use with caution)
Claude Desktop Issues
- Restart Claude Desktop after config changes
- Validate JSON config syntax
- Check console logs for errors
Common Errors
- "import: command not found": Update to latest version
- Authentication failed: Verify credentials and permissions
- SSL errors: Check CA certificate or disable SSL validation
- 403 from
/api/console/proxywhile searching Elasticsearch: Usesearch_elasticsearch. The Console proxy can require the Kibana Dev Tools privilege even when the user has permission to read the target indices.
🔍 Debugging
Use MCP Inspector for debugging:
This provides a browser-accessible debugging interface.
📦 Package Information
- NPM: @tocharianou/mcp-server-kibana
- GitHub: TocharianOU/mcp-server-kibana
- Node.js: >= 18.0.0
- License: Apache 2.0
🤝 Contributing
This project is community-maintained. Contributions and feedback are welcome!
Please follow the Elastic Community Code of Conduct in all communications.
📄 License
Apache License 2.0 - See LICENSE file for details.
來源:README.md,提交 1e66edb
工具
0版本歷史
3- v0.11.1最新Oct 11, 2026
- v0.11.0Oct 11, 2026
- v0.10.2Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分