Skip to main content
Glama
Kibana Log Analysis & API Dashboard MCP Server

Kibana Log Analysis & API Dashboard MCP Server

by sid-s-s

Kibana Log Analysis & API Dashboard MCP Server

An MCP (Model Context Protocol) server designed for enterprise developers to connect local AI assistants directly to Elasticsearch, Kibana, and local codebases.

⚠️ For New Developers & Forkers

If you have just cloned this repository to use within your organization, search the codebase for TODO: comments. There are several places where data or settings should be manually updated to fit your company's architecture.

The most crucial manual updates inside src/index.ts include:

  1. Log Schema Customization: Update the .level or http.response.status_code fields to match your company's logging convention.

  2. Self-Signed Certificates: Add your internal CA cert path if your Elasticsearch instance does not use public SSL certificates.

  3. Regex Parsers for .NET or Go: If your team uses languages other than Java/Typescript, update the scan_code_for_apis tool regex.

Related MCP server: Smart Coding MCP

Features

  • search_logs: Search Elasticsearch indices using keywords and Lucene queries.

  • get_log_details: Retrieve the full un-truncated JSON of specific log events.

  • analyze_service_health: Aggregate error rates, success rates, and HTTP status codes for a given service.

  • scan_code_for_apis: Scans your local Spring Boot (Java) or Express (Node.js) project to dynamically discover REST endpoints.

  • create_api_dashboard: Programmatically generates a Kibana dashboard visualizing the dynamically discovered endpoints using the Kibana Saved Objects API.

Installation & Production Setup

  1. Ensure you have Node.js (v18+) installed.

  2. Run npm install

  3. Run npm run build

  4. Copy .env.example to .env and configure your environment variables (or set them directly in your LLM Client setup).

Configuration Map

Variable

Description

ELASTIC_URL

URL to your Elasticsearch cluster (e.g., https://es.internal:9200)

ELASTIC_API_KEY

Auth Token with specific read scopes.

KIBANA_URL

URL to your Kibana instance.

Usage with Claude Desktop / Cursor

Add the following configuration to your claude_desktop_config.json or Cursor MCP settings:

{
  "mcpServers": {
    "kibana-logs": {
      "command": "node",
      "args": ["/Users/sidhu/.gemini/antigravity/scratch/kibana-mcp-server/build/index.js"],
      "env": {
        "ELASTIC_URL": "https://your-bank-cluster:9200",
        "ELASTIC_API_KEY": "your_secure_api_key",
        "KIBANA_URL": "https://your-bank-kibana:5601"
      }
    }
  }
}

Security Best Practices for Enterprise

  • Least Privilege: Do not grant your ELASTIC_API_KEY delete, put, or cluster-admin privileges. It only needs read on application indices, and all access to the Kibana Saved Objects API (to create dashboards).

  • Data Masking: If your logs contain PII (Personally Identifiable Information), you should implement a regex mask in src/index.ts right before returning the logs to the AI payload.

Available Tools

5 tools
analyze_service_healthB

Aggregate logs to determine error vs. success rates

Inputs: index (required), hoursBack (required), serviceName (required).

create_api_dashboardA

Generate a Kibana Dashboard tracking specific endpoints

Inputs: endpoints (required), dashboardName (required).

get_log_detailsB

Retrieve the full, raw JSON of a specific log event

Inputs: index (required), documentId (required).

scan_code_for_apisB

Scans a local project directory to discover REST APIs

Inputs: projectPath (required).

search_logsB

Search logs matching keywords within a time range

Inputs: index (required), keyword (required), hoursBack (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: searching logs, retrieving details, analyzing health, scanning APIs, and creating dashboards. No overlap between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_logs, get_log_details), making them predictable and easy to distinguish.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its dual focus on log analysis and API dashboard creation, without being too sparse or overloaded.

    Completeness4/5

    Core workflows are covered (search, details, health analysis, API discovery, dashboard creation), but minor gaps exist—e.g., missing tools for listing, updating, or deleting dashboards.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to perform semantic code search across a local codebase by meaning rather than exact keywords, using local AI embeddings with flexible dimensions. It also provides indexing, cache management, workspace switching, package version lookup, and server status tools.
      114 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to perform intelligent semantic code search across a codebase using local AI embeddings, with tools for reindexing, cache management, workspace switching, package version lookup, and status checks.
      114 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to search a codebase by meaning using local AI embeddings, finding relevant code even when terminology differs from the query. Also provides package version lookup across 20+ registries, workspace switching, reindexing, cache clearing, and status checks.
      114 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to search local codebases semantically by meaning, automatically indexing code and returning relevant chunks even when terminology differs. It also supports package version lookup, workspace switching, reindexing, cache clearing, and server status checks.
      114 npm
      MIT