What are the prerequisites for using this setup?
You need Docker and Docker Compose, Python 3.x, pipx, and the LLM clients (Amazon Q CLI or Anthropic Claude Desktop).
@madhankb
Basic information
Step by step guide for integrating LLMs with OpenSearch MCP servers
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"opensearch-mcp-integration": {
"command": "docker",
"args": [
"compose",
"up",
"-d"
]
}
}
}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.
This guide provides step-by-step instructions for integrating Amazon Q and Anthropic Claude Desktop with OpenSearch using MCP servers, enabling natural language interactions with an OpenSearch cluster. It covers setting up a local OpenSearch instance, installing the opensearch-mcp-server, configuring LLM clients, and using natural language commands to manage indices and documents.
Install the MCP server via pipx install opensearch-mcp-server. Configure your LLM client by creating a JSON file (mcp.json for Amazon Q or claude_desktop_config.json for Claude Desktop) with the command path and environment variables (OPENSEARCH_URL, OPENSEARCH_SSL_VERIFY, OPENSEARCH_USERNAME, OPENSEARCH_PASSWORD). Start a local OpenSearch instance using the provided docker-compose.yml, then use natural language prompts in the LLM to perform operations like creating indices, adding documents, and searching.
You need Docker and Docker Compose, Python 3.x, pipx, and the LLM clients (Amazon Q CLI or Anthropic Claude Desktop).
Create a `docker-compose.yml` with the provided configuration and run `docker compose up -d`. The instance will be available on ports 9200 and 9600.
The server exposes tools including `list_indices`, `get_index`, `create_index`, `delete_index`, `search_documents`, `index_document`, `get_document`, `delete_document`, `delete_by_query`, `get_cluster_health`, `get_cluster_stats`, `list_aliases`, `get_alias`, `put_alias`, `delete_alias`, and `general_api_request`.
Create a JSON configuration file (e.g., `~/.aws/amazonq/mcp.json` for Amazon Q or the Claude Desktop config path) with the `opensearch-mcp-server` command and environment variables for the OpenSearch URL, credentials, and SSL settings.
Use strong passwords in production, enable SSL, and regularly rotate credentials. The guide defaults to SSL verification disabled for local testing, but this should be removed in production.
An official Qdrant Model Context Protocol (MCP) server implementation
Postgres MCP Pro provides configurable read/write access and performance analysis for you and your AI agents.
A MCP (model context protocol) server that gives the LLM access to and knowledge about relational databases like SQLite, Postgresql, MySQL & MariaDB, Oracle, and MS-SQL.

Local database MCP server: your agent sees a migration's impact before it runs, for PostgreSQL, MySQL, SQL Server and SQLite, with no database credentials.
Connect ClickHouse to your AI assistants.
Comments