Kibana MCP Server

API Specification

This project is based on the official Elastic Kibana API documentation and uses the OpenAPI YAML specification from Elastic Stack 8.x (ES8) to dynamically retrieve and manage all Kibana API endpoints. For the latest details, see the Kibana API documentation.

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 community-maintained and is not an official product of Elastic or MCP.

Features

• Connect to local or remote Kibana instances

• Secure authentication (username/password)

• SSL/TLS and custom CA certificate support

• Exposes Kibana API endpoints as both tools and resources

• Search, view, and execute Kibana APIs from MCP clients

• Type-safe, extensible, and easy to integrate

Directory Structure

Resources

Examples:

• kibana-api://paths?search=saved_objects

• kibana-api://path/GET/%2Fapi%2Fstatus

Tools

Prompts

Configuration

Configure the server via environment variables:

Usage

Start the Server

Example MCP Client Configuration

Add to the Claude Desktop config file (MacOS path: ~/Library/Application Support/Claude/claude_desktop_config.json):

Example Queries

• "What is the status of my Kibana server?"

• "List all available Kibana API endpoints."

• "Show details for the POST /api/saved_objects/_find endpoint."

• "Execute a custom API request for /api/status."

• "Get a list of all dashboards in Kibana."

• "Query API endpoints related to endpoint events."

• "List all case-related API endpoints."

• "Create a new case in Kibana."

• "Create a new dashboard in Kibana."

Two Prompt Modes in Claude Desktop

When using this server with Claude Desktop, two different prompt interaction modes are supported:

1. Tool-based Prompt Mode

• How it works: Claude Desktop can directly call server tools (such as get_status, execute_api, search_kibana_api_paths, etc.) to answer your questions or perform actions.

• Best for: Users who want a conversational, guided experience. The server will automatically search, execute, and explain Kibana APIs.

• Example: "Show all Kibana API endpoints related to saved objects."

• Testing tip: Select the kibana-tool-expert prompt in Claude Desktop for integration testing, then start using it.

2. Resource-based Prompt Mode

• How it works: Claude Desktop interacts with the server via resource URIs (such as kibana-api://paths or kibana-api://path/GET/%2Fapi%2Fstatus), and the server returns structured data for Claude to parse.

• Best for: Advanced users, MCP clients that only support resource access, or programming scenarios needing raw API metadata.

• Example: "Get resource kibana-api://paths?search=dashboard"

Note: The two endpoints in resources (kibana-api://paths and kibana-api://path/{method}/{encoded_path}) have corresponding base tools (list_all_kibana_api_paths, get_kibana_api_detail). This design ensures compatibility with MCP clients that cannot intelligently select multiple resources, making it easier for tools like Claude Desktop to interact with Kibana.

Tip: Most users are recommended to use tool mode for a more natural and powerful experience; resource mode offers maximum flexibility for advanced and compatibility use cases.

Development

Install dependencies:

Build the server:

Auto-rebuild in development mode:

Debugging

Since the MCP server communicates via stdio, debugging can be inconvenient. It is recommended to use MCP Inspector:

After starting, Inspector will provide a browser-accessible debugging tool URL.

Community

This project is community-maintained. Contributions and feedback are welcome! Please be respectful and inclusive in all communications, and follow the Elastic Community Code of Conduct.

License

This project is licensed under the Apache License 2.0. See the LICENSE file for details.

Troubleshooting

• Check if MCP configuration is correct

• Ensure the Kibana address is accessible

• Verify authentication credentials have sufficient permissions

• If using a custom CA, ensure the certificate path is correct and readable

• If using NODE_TLS_REJECT_UNAUTHORIZED=0, be aware of security risks

• Check error messages output in the terminal