MCP.so
Sign In

OpenSearch MCP Server

@showjason

Basic information

Category

Databases

License

MIT license

Transports

stdio

Author

showjason

About OpenSearch MCP Server

No overview available yet

OpenSearch MCP Server config

Add this server to your MCP-compatible client using the configuration below.

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

OpenSearch MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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.

Frequently asked questions

1

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.

2

What are the runtime dependencies?

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

3

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.

4

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.

5

Are there any known limitations?

The README does not mention specific limitations.

Comments

More Databases MCP servers