Skip to main content
Glama
opensearch-project

opensearch-mcp-server-py

Official

Related Servers

Alternatives to opensearch-mcp-server-py

No user-submitted related servers found.

    Related Servers

    • 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.
      199 npm
      MIT
    • 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
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with OpenSearch clusters for searching indices, retrieving mappings, and managing shards through the MCP protocol.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to directly interact with Elasticsearch for searching, aggregating, and retrieving documents from indices, supporting full-text search, semantic search, and various query modes.
      20 npm
      MIT
    • 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

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct actions such as listing indices, retrieving mappings, searching, counting, and checking cluster health. GenericOpenSearchApiTool intentionally overlaps with every dedicated tool, and MsearchTool overlaps somewhat with SearchIndexTool, but the descriptions provide enough guidance to choose correctly.

    Naming Consistency4/5

    All tool names use PascalCase with a Tool suffix, and most follow a Verb+Noun pattern like ListIndexTool, SearchIndexTool, and GetShardsTool. IndexMappingTool and ClusterHealthTool lack explicit action verbs, and MsearchTool uses an abbreviated name, so the pattern is not perfectly consistent.

    Tool Count5/5

    Nine tools is a well-scoped count for an OpenSearch server covering search, mappings, cluster health, shards, counts, and a generic API fallback. Each dedicated tool earns its place, and the count is comfortably within the ideal range.

    Completeness4/5

    The dedicated tools cover common read, search, and monitoring workflows well, and GenericOpenSearchApiTool provides an escape hatch for any unsupported endpoint. However, common operations like creating/deleting indices or document-level CRUD lack dedicated first-class tools, so coverage relies partly on the generic fallback.

    Maintenance

    ActivityNo data
    ResponsivenessWithin a week