Skip to main content
Glama
seohyunjun

OpenSearch MCP Server

by seohyunjun

Related Servers

Alternatives to OpenSearch 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
      B
      quality
      D
      maintenance
      opensearch-mcp-server-py is a Model Context Protocol (MCP) server for OpenSearch that enables AI assistants to interact with OpenSearch clusters. It provides a standardized interface for AI models to perform operations like searching indices, retrieving mappings, and managing shards through both stdio and streaming (SSE/Streamable HTTP) protocols.
      11
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for OpenSearch that enables AI assistants to interact with OpenSearch clusters through a standardized interface for search, index management, and cluster operations.
      9
      77,891 PyPI
      151
      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
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to interact with OpenSearch, including searching indices, managing documents, creating and deleting indexes, checking cluster health, and monitoring statistics.
      23 npm
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Context-efficient MCP server that executes OpenSearch DSL queries and returns synthesized output instead of raw JSON, reducing token usage by up to 90%.
      3
      -

    TDQS

    B3.1/5.0

    Scored across 14 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific OpenSearch operations. There is no overlap between tools like get_cluster_health (health status), get_mapping (index structure), and search_documents (document queries). Each tool name precisely indicates its unique function within the OpenSearch domain.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern throughout. The pattern is predominantly 'get_' for retrieval operations and 'list_' for listing operations, with specific exceptions like 'generate_' and 'search_' that maintain the same structure. No mixing of conventions like camelCase or snake_case variations.

    Tool Count5/5

    With 14 tools, this server is well-scoped for OpenSearch operations, covering monitoring, configuration, and data querying aspects. Each tool earns its place by addressing distinct needs like cluster health, index management, and document search, without being overly sparse or bloated.

    Completeness4/5

    The tool set provides strong coverage for monitoring, configuration retrieval, and search operations in OpenSearch. Minor gaps exist, such as the absence of tools for creating or updating resources (e.g., indices, policies), but agents can still perform core read and diagnostic workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues