Skip to main content
Glama
cr7258

Elasticsearch MCP Server

Related Servers

Alternatives to Elasticsearch MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to interact with Elasticsearch clusters, allowing them to manage indices and execute search queries using natural language.
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure and efficient interaction with Elasticsearch clusters through the Model Context Protocol, providing tools for data management, search, and export.
      53 npm
      1
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      Connects to Elasticsearch clusters through the Model Context Protocol, enabling natural language querying and management of Elasticsearch data. Provides tools to search indices, list available indices, and retrieve index mappings.
      3
      -
    • A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Elasticsearch clusters for health checks, index management, document CRUD operations, and search via natural language.
      10
      11 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Connects to Elasticsearch databases using the Model Context Protocol, allowing users to query and interact with their Elasticsearch indices through natural language conversations.
      4
      19 npm
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to connect to and interact with Elasticsearch 7.x clusters through natural language, supporting search, indexing, mappings, templates, cluster health, and optional diagnostic or destructive tools.
      17
      MIT

    TDQS

    A3.6/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., create_index, delete_document, get_cluster_health), with no ambiguity between them. Even similar operations like get_alias and list_aliases are clearly separated by singular vs. plural scope.

    Naming Consistency5/5

    All tools follow a strict verb_noun pattern in lower_snake_case (e.g., create_data_stream, search_documents), with no mixing of conventions. The verbs are consistent: create, delete, get, list, put, search, analyze, index, general.

    Tool Count4/5

    With 20 tools, the server is slightly over the ideal 3-15 range but still reasonable for a comprehensive Elasticsearch integration. Each tool covers a meaningful operation without feeling excessive.

    Completeness3/5

    Core CRUD operations for indices, documents, data streams, and aliases are covered, but notable gaps exist: no explicit update document (only full replacement via index_document), no update_by_query, and no mapping or settings update tools. The general_api_request can fill gaps but is a workaround.

    Maintenance

    ActivitySlowing
    ResponsivenessWithin a week