Skip to main content
Glama
vanovarderesyan

Elastic MCP Server

by vanovarderesyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Elastic MCP Server

No user-submitted related servers found.

    Related Servers

    • elasticsearch-logs

      ws135y
      F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for Elasticsearch log querying. Enables natural language search, filtering, context retrieval, and aggregation of logs.
      -

    • quickwit-mcp

      agarwalvivek29
      A
      license
      Not graded
      quality
      F
      maintenance
      A read-only MCP server that exposes Quickwit log search and aggregations to LLM clients, enabling natural language log investigation.
      Apache 2.0

    • mcp-opensearch

      bunnyiesart
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that enables AI assistants to search, aggregate, and explore OpenSearch log data through 12 tools for connectivity, index discovery, search, and aggregations.
      17
      MIT

    • Graylog MCP Server

      jagadeesh52423
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives AI assistants direct access to your Graylog logs -- search, aggregate, analyze, and cluster log data through natural language.
      23
      16 npm
      MIT

    • elastic-security-mcp

      AndreuCrespo
      A
      license
      Not graded
      quality
      C
      maintenance
      A Python MCP server that provides AI agents with a controlled, read-first interface to Elasticsearch, Kibana Security, Fleet, and Elastic Defend.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation3/5

    Most tools have clear, distinct roles, but list_indices, list_data_views, and cluster_health all surface data-view/index information and could be confused during discovery. The remaining search, aggregate, mapping, and document tools are well separated.

    Naming Consistency4/5

    The tool names mostly follow a predictable verb_noun pattern: list_*, get_*, search_*, and aggregate_*. cluster_health is the main outlier, since it reads as a noun phrase rather than an imperative action like the others.

    Tool Count4/5

    Seven tools is a reasonable size for a focused Kibana/Elasticsearch log server. The count is slightly higher than necessary because listing functionality is split across multiple overlapping tools.

    Completeness5/5

    The toolset covers the full log-exploration workflow: discover data sources, inspect mappings, search logs, aggregate logs, and fetch individual documents. Health checking is also present, so agents can verify connectivity without hitting a dead end.

    Resources