Skip to main content
Glama
awesimon

Elasticsearch MCP Server

by awesimon

Related Servers

Alternatives to Elasticsearch MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Connects Claude and other MCP clients to Elasticsearch data, allowing users to interact with their Elasticsearch indices through natural language conversations.
      3
      1,690 npm
      718
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects agents to Elasticsearch data using the Model Context Protocol, allowing natural language interaction with Elasticsearch indices through tools for listing indices, getting field mappings, performing searches, and viewing shard information.
      1,690 npm
      Apache 2.0
    • 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
      5 npm
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Facilitates interaction with Elasticsearch clusters by allowing users to perform index operations, document searches, and cluster management via a Model Context Protocol server and natural language commands.
      20
      307
      Apache 2.0
    • 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
      -
    • 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
      -

    TDQS

    B3/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct Elasticsearch resource and action (e.g., create_index, create_mapping, search, bulk). There is no overlap or ambiguity; tools are clearly differentiated by their purpose.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern with underscores (e.g., create_index, get_mappings). However, 'elasticsearch_health' deviates by starting with a noun instead of a verb, causing a minor inconsistency.

    Tool Count5/5

    With 11 tools, the server covers a reasonable breadth of Elasticsearch operations (index management, search, mapping, templates) without being excessive. The count fits well within the typical 3-15 range for a focused server.

    Completeness2/5

    The tool set lacks essential operations like deleting an index and document-level CRUD (get, delete by ID). While bulk and search are present, agents cannot perform complete lifecycle management, leading to significant gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues