Repository navigation
Releases
v0.11.1 - Security: HTTP Mode Authentication, CA Certificate Fix
Security and bug-fix release — upgrading is recommended
Fixed: KIBANA_CA_CERT prevented the server from starting
The CA certificate was loaded with require() inside an ES module, which always threw. Any configuration that set KIBANA_CA_CERT failed at startup with "Failed to load CA certificate", even with a valid file. Custom CA certificates now work.
HTTP mode: authentication and Host validation
Every session on /mcp acts with the Kibana credentials the server was started with. Until now the endpoint accepted any client that could reach the port.
MCP_BEARER_TOKEN(new): when set, every/mcprequest must sendAuthorization: Bearer <token>; otherwise the server answers401./healthstays open.- Host header validation: when bound to a loopback address (the default), requests whose
Hostheader is not a loopback name are rejected with403. This blocks DNS rebinding attacks from a web page against a local server. MCP_ALLOWED_HOSTS(new): extra hostnames to accept, comma-separated.- Listening on a non-loopback address without
MCP_BEARER_TOKENnow logs a warning at startup. It still starts, so existing deployments keep working.
Behavior change: if you run the server bound to localhost behind a reverse proxy that forwards its public Host header, add that hostname to MCP_ALLOWED_HOSTS, or requests will get 403.
Dependencies
@modelcontextprotocol/sdkraised to ^1.32.1 (GHSA-6qxp-vccf-f47h). The advisory is in the SDK's OAuth client, which this server does not use.proxy-addr2.0.8 (GHSA-jqcg-44mw-7w3h).npm audit --omit=dev: 0 vulnerabilities.
Documentation
search_elasticsearchis described more precisely: it is read-only and Elasticsearch enforces the configured user's index privileges on every search. It does not widen data access.
Tested against
Kibana 8.17.3, 8.19.15 and 9.5.0. search_elasticsearch is now confirmed working on Kibana 9.5.
Full Changelog: v0.11.0...v0.11.1
v0.11.0 - Elasticsearch Search Tool
New: search_elasticsearch
Search Elasticsearch documents, logs and aggregations with Query DSL through Kibana's /internal/search/es endpoint (#16, @Akilaydin).
This helps when a Kibana user can read the target indices but cannot use Dev Tools: /api/console/proxy returns 403 for such users, while this tool works with their existing Elasticsearch permissions.
- Verified on Kibana 8.8.2 (restricted user: Console proxy returned 403, this tool returned documents from the same indices) and Kibana 8.19.15
- Rejects wildcard-only index segments (
*,**,_all, including inside comma-separated expressions), an empty body, andbody.sizeabove 100 - Marked read-only via MCP tool annotations
/internal/search/esis an internal Kibana API, so its contract can change between Kibana versions. It has not been tested on Kibana 9.x
Behavior change
Paths starting with /internal/ are now space-prefixed in non-default spaces, the same as /api/ paths. This applies to every tool, including execute_kb_api. Previously such requests were sent to the default space regardless of the space argument.
Improvements
- Tool errors now include the HTTP status code and Kibana's response details instead of only the transport error text
npm testworks again:jest.config.jsrenamed tojest.config.cjs
Full Changelog: v0.10.2...v0.11.0
v0.10.2 - Security: Prevent Credential Leak via execute_kb_api
Security release — upgrading is recommended
Fixed: Kibana credentials could be sent to a non-Kibana host
execute_kb_api accepted any string as path. On Kibana installed at the root path, an absolute URL (e.g. http://other-host/...) bypassed the configured Kibana base URL, and the request was sent to that host with the configured API key or basic-auth credentials attached. An agent that was prompt-injected via content stored in Kibana could be steered into making such a call.
execute_kb_apinow rejects anypaththat is not a Kibana API path starting with a single/- The HTTP client additionally sets
allowAbsoluteUrls: false, so no tool can send requests outside the configured Kibana origin
Dependencies
- Raised minimum versions:
axios^1.20.0,js-yaml^4.3.2,ajv^8.20.0 npm audit: 0 vulnerabilities
Fixed: KIBANA_TIMEOUT was ignored
The variable was read but never applied; the client always used 60000ms. It is now honored. The default stays at 60000ms (the value actually in effect), and the README is corrected.
Full Changelog: v0.10.1...v0.10.2
v0.10.1 - Retry-Safety Guidance Reaches the Generic API Tool
What's Changed
Follow-up to v0.10.0, closing the gap the retry-safety work left open in the system prompt:
- The worked example in
src/prompts.tsrecommendedexecute_api, which is not a registered tool. It now points atvl_create_saved_objectwith a caller-chosen stable id — the tool that documents the safe pattern (#14, #15, @aurumflux20) execute_kb_apinow carries a short version of the same retry-safety warning. It can reach any write endpoint, so it should not be the one path with no guidance on it
No behavior changes; both edits are strings the model reads.
Full Changelog: v0.10.0...v0.10.1
v0.10.0 - Retry-Safety Documentation for Saved-Object Creation
What's Changed
Documentation-only release focused on retry safety of vl_create_saved_object:
- The
idparameter description now explains that omitting it makes retries unsafe: a retry after a timeout creates a second object with a new auto-generated id (#12, @aurumflux20) - The 409 conflict message now advises verifying with
vl_get_saved_objectfirst and keeping a stable caller-chosen id, instead of suggesting to omit the id (#13, @aurumflux20) - Fixed a PUT/POST slip in the new docstring: create-with-id is
POST /api/saved_objects/{type}/{id}
No behavior changes.
Full Changelog: v0.9.0...v0.10.0
v0.9.0 - MCP SDK 1.29.0 Upgrade
Upgrades: @modelcontextprotocol/sdk 1.18.2 -> 1.29.0; zod 3.24.2 -> 3.25.76; added @cfworker/json-schema 4.1.1 (new SDK peer dependency). Fixes: McpServer capabilities were passed in the wrong constructor argument and silently ignored, now correctly applied; removed invalid transport field; server info no longer reports a hardcoded stale version 0.7.3. Verified against Kibana 8.17.3: protocol handshake, 10 tools, prompts, resources, and HTTP transport all working. Install: npx @tocharianou/mcp-server-kibana
v0.8.0 - Kibana 9 Compatibility & Sub-path URL Fix
Fixes: sub-path KIBANA_URL 401 on non-root installations; x-elastic-internal-origin header for Kibana 9; Kibana 9 internal API access; corrected npm scope to @tocharianou/mcp-server-kibana. Install: npx @tocharianou/mcp-server-kibana
v0.7.3 - Hash Verification & Improvements
✨ What's New
Security & Integrity
- Hash Verification: Added SHA256 and SHA512 checksum generation for release packages
- Package integrity can now be verified with
shasum -a 256 -corshasum -a 512 -c
Code Quality
- English-Only Codebase: Removed all Chinese comments, replaced with English
- Cleaner Documentation: Streamlined README by removing unnecessary technical details
Release Process
- Enhanced release script with automatic hash generation
- Added verification commands in release output
- Improved package validation workflow
📦 Installation
npm install -g @tocharianou/mcp-server-kibana@0.7.3🔐 Package Verification
# Download the release tarball
wget https://github.com/TocharianOU/mcp-server-kibana/releases/download/v0.7.3/mcp-server-kibana-v0.7.3.tar.gz
# Download checksums
wget https://github.com/TocharianOU/mcp-server-kibana/releases/download/v0.7.3/mcp-server-kibana-v0.7.3.tar.gz.sha256
wget https://github.com/TocharianOU/mcp-server-kibana/releases/download/v0.7.3/mcp-server-kibana-v0.7.3.tar.gz.sha512
# Verify package integrity
shasum -a 256 -c mcp-server-kibana-v0.7.3.tar.gz.sha256
shasum -a 512 -c mcp-server-kibana-v0.7.3.tar.gz.sha512📋 Changes
- Add SHA256/SHA512 hash generation to release script
- Update version to 0.7.3 across all files
- Remove all Chinese comments (English only)
- Streamline README.md documentation
- Improve release process with checksum validation
🔗 Links
- NPM Package: https://www.npmjs.com/package/@tocharianou/mcp-server-kibana
- Documentation: https://github.com/TocharianOU/mcp-server-kibana#readme
- MCP Registry: https://github.com/modelcontextprotocol/servers
v0.7.2
v0.7.2
- Version alignment with Elasticsearch MCP
- Ready-to-use package with all dependencies included (9MB)
- Includes Kibana OpenAPI schema and logos
- No npm install required after extraction
Download: mcp-server-kibana-v0.7.2.tar.gz
Usage:
tar -xzf mcp-server-kibana-v0.7.2.tar.gz
KIBANA_URL=https://localhost:5601 node dist/index.jsv0.7.0 - Complete Release Package Support
🚀 Release v0.7.0 - Complete Release Package Support
This release introduces a new standalone packaging system that includes all dependencies, making deployment easier.
📦 What's New
Complete Release Packaging
- Ready-to-use packages: Includes all production dependencies (
node_modules) - No installation required: Extract and run immediately with
node dist/index.js - Flat directory structure: Easy deployment and integration
- Optimized size: Automatically removes test files and unnecessary documentation from dependencies
- MCP Registry Configuration: Added
server.jsonfor MCP Registry compliance
🎯 Usage
Download and Extract
wget https://github.com/TocharianOU/mcp-server-kibana/releases/download/v0.7.0/mcp-server-kibana-v0.7.0.tar.gz
mkdir mcp-server-kibana && cd mcp-server-kibana
tar -xzf ../mcp-server-kibana-v0.7.0.tar.gzRun Directly
KIBANA_URL=https://localhost:5601 KIBANA_API_KEY=your-key node dist/index.jsUse with MCP Clients
Add to your MCP client configuration:
{
"kibana": {
"command": "node",
"args": ["/path/to/mcp-server-kibana/dist/index.js"],
"env": {
"KIBANA_URL": "https://localhost:5601",
"KIBANA_API_KEY": "your-api-key"
}
}
}📋 Release Assets
- mcp-server-kibana-v0.7.0.tar.gz (~9MB): Complete package with all dependencies
🔧 For Developers
To create your own release package:
npm run releaseSee RELEASE.md for detailed instructions.
✨ Features Included
- Dynamic API discovery via OpenAPI schema
- Comprehensive Elastic Stack integration
- Multiple transport modes (stdio, HTTP)
- Security-focused tools for incident investigation
- Dashboard and visualization management
- Logs, metrics, and APM support
Full Changelog: v0.6.2...v0.7.0