OpenSearch MCP Server

Name: OpenSearch MCP Server
Author: showjason

@showjason

代码仓库

关于 OpenSearch MCP Server

暂无概览

基本信息

分类

数据库

许可证

MIT license

运行时

python

传输方式

stdio

发布者

showjason

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "opensearch-mcp-server-showjason": {
      "command": "python",
      "args": [
        "-m",
        "venv",
        ".venv"
      ]
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is OpenSearch MCP Server?

A Model Context Protocol (MCP) server that provides tools for interacting with an OpenSearch cluster. It lets you manage indices, monitor cluster health, and search documents through MCP‑compatible AI assistants.

How to use OpenSearch MCP Server?

Clone the repo, create a Python virtual environment, and install with uv. Configure a .env file with your OpenSearch host, username, and password. Run the server with uv run opensearch-mcp-server --port=<port>, then integrate it with Cursor or Claude Desktop using the provided MCP config snippets.

Key features of OpenSearch MCP Server

List all indices in an OpenSearch cluster
Get index mapping and settings
Show cluster health status
Retrieve cluster statistics
Search documents

Use cases of OpenSearch MCP Server

Use an AI assistant to check OpenSearch cluster health via natural language.
Search for documents without writing raw queries.
Automate index management tasks (e.g., inspecting mappings) through MCP tools.

FAQ from OpenSearch MCP Server

How does this server differ from elasticsearch-mcp-server?

It is inspired by elasticsearch-mcp-server but built specifically for OpenSearch, using OpenSearch endpoints and authentication.

What are the runtime dependencies?

Python, uv, and a running OpenSearch cluster. The server uses the uv package manager for installation.

Where does the data live?

All data stays in your OpenSearch cluster; the server only acts as a bridge between MCP clients and the cluster.

What transport or authentication does the server use?

The server listens on a configurable port for SSE (Server‑Sent Events) connections. Authentication is done via username/password set in the .env file.