Skip to main content
Glama
Octodet

octodet-elasticsearch-mcp

by Octodet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to octodet-elasticsearch-mcp

No user-submitted related servers found.

    Related Servers

    • Elasticsearch MCP Server

      sajitsasi
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides tools and resources to interact with Elasticsearch clusters, including listing indices, searching, and retrieving mappings.
      3
      MIT

    • Elasticsearch/OpenSearch MCP

      Rbedoyag
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables interaction with Elasticsearch and OpenSearch clusters for searching documents and managing indices. It provides tools for cluster health monitoring, index configuration, and general API requests.
      16
      Apache 2.0

    • 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.
      -

    • elastic-mcp

      csimi
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol server for Elasticsearch, enabling search, index inspection, and cluster information tools with optional write tools.
      14
      19 npm
      1
      ISC

    • elastic-mcp

      jrvalinas
      A
      license
      B
      quality
      D
      maintenance
      Small production-oriented MCP server for diagnosing incidents from Elasticsearch logs with unknown schema. It provides tools for log discovery, retrieval, and issue diagnosis.
      6
      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.5/5.0

    Scored across 16 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific Elasticsearch operations with no ambiguity. For example, 'add_document' vs 'update_document' vs 'delete_document' are clearly differentiated, and cluster operations like 'get_cluster_health' are separate from index operations like 'list_indices'.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern throughout, using snake_case consistently. The naming convention is predictable with clear action-object pairs like 'create_index', 'delete_document', 'get_mappings', and 'list_indices'.

    Tool Count4/5

    16 tools is slightly on the higher side but reasonable for an Elasticsearch MCP server that needs to cover document operations, index management, cluster monitoring, and search functionality. The count feels comprehensive without being excessive for the domain.

    Completeness5/5

    The tool set provides complete coverage of Elasticsearch operations including full CRUD for documents (add, update, delete, get via search), index lifecycle management (create, delete, list), cluster monitoring, and advanced operations like bulk processing and query-based updates/deletes. No obvious gaps exist for core Elasticsearch workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources