[{"_1":2,"_326":-5,"_327":-5},"loaderData",{"_3":4,"_22":23,"_267":268},"root",{"_5":6,"_7":8},"toasts",[],"visitor",{"_9":10,"_11":12},"viewportWidth",1280,"visitorSession",{"_13":14,"_16":17,"_18":-5,"_19":20,"_21":-5},"attributes",[15],"bot","id",14674407,"membership","referenceId","0199368b-156e-7599-a55d-ca69a5c1bb1e","userAccount","routes/_public/mcp/servers/~namespace/~slug/_pages/_layout",{"_24":25,"_80":-5,"_81":38,"_27":82,"_183":184,"_265":266},"availableLocales",[26,38,45,52,59,66,73],{"_27":28,"_31":35,"_36":37},"mcpServer",{"_29":30,"_31":32,"_33":34},"description","Verbindet Claude und andere MCP-Clients mit Elasticsearch-Daten und ermöglicht Benutzern die Interaktion mit ihren Elasticsearch-Indizes über Konversationen in natürlicher Sprache.","name","Elasticsearch MCP-Server","readme","# Elasticsearch MCP-Server\n\nDieses Repository enthält experimentelle Funktionen, die für Forschung und Evaluierung bestimmt sind und nicht produktionsreif sind.\n\nStellen Sie mithilfe des Model Context Protocol (MCP) direkt von jedem MCP-Client (wie Claude Desktop) eine Verbindung zu Ihren Elasticsearch-Daten her.\n\nDieser Server verbindet Agenten über das Model Context Protocol mit Ihren Elasticsearch-Daten. Er ermöglicht Ihnen die Interaktion mit Ihren Elasticsearch-Indizes über natürliche Sprachkonversationen.\n\n## Verfügbare Tools\n\n* `list_indices` : Listet alle verfügbaren Elasticsearch-Indizes auf\n* `get_mappings` : Ruft Feldzuordnungen für einen bestimmten Elasticsearch-Index ab\n* `search` : Führen Sie eine Elasticsearch-Suche mit der bereitgestellten Abfrage-DSL durch\n* `get_shards` : Shard-Informationen für alle oder bestimmte Indizes abrufen\n\n## Voraussetzungen\n\n* Eine Elasticsearch-Instanz\n* Elasticsearch-Authentifizierungsdaten (API-Schlüssel oder Benutzername/Passwort)\n* MCP-Client (z. B. Claude Desktop)\n\n## Demo\n\n\n\n## Installation und Einrichtung\n\n### Verwenden des veröffentlichten NPM-Pakets\n\n> \\[!TIP] Am einfachsten lässt sich der Elasticsearch MCP-Server über das veröffentlichte npm-Paket verwenden.\n\n1. **MCP-Client konfigurieren**\n\n * Öffnen Sie Ihren MCP-Client. Sehen Sie sich die [Liste der MCP-Clients](https://modelcontextprotocol.io/clients) an. Hier konfigurieren wir Claude Desktop.\n * Gehen Sie zu **Einstellungen > Entwickler > MCP-Server**\n * Klicken Sie auf `Edit Config` und fügen Sie einen neuen MCP-Server mit der folgenden Konfiguration hinzu:\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@elastic/mcp-server-elasticsearch\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n2. **Eine Unterhaltung beginnen**\n\n * Öffnen Sie eine neue Konversation in Ihrem MCP-Client\n * Der MCP-Server sollte automatisch eine Verbindung herstellen\n * Sie können jetzt Fragen zu Ihren Elasticsearch-Daten stellen\n\n### Konfigurationsoptionen\n\nDer Elasticsearch MCP-Server unterstützt Konfigurationsoptionen zum Herstellen einer Verbindung mit Ihrem Elasticsearch:\n\n> \\[!NOTE] Sie müssen zur Authentifizierung entweder einen API-Schlüssel oder sowohl Benutzernamen als auch Kennwort angeben.\n\n| Umgebungsvariable | Beschreibung | Erforderlich |\n| ----------------- | -------------------------------------------------------------------- | ------------ |\n| `ES_URL` | Die URL Ihrer Elasticsearch-Instanz | Ja |\n| `ES_API_KEY` | Elasticsearch-API-Schlüssel zur Authentifizierung | NEIN |\n| `ES_USERNAME` | Elasticsearch-Benutzername für die Basisauthentifizierung | NEIN |\n| `ES_PASSWORD` | Elasticsearch-Passwort für die Basisauthentifizierung | NEIN |\n| `ES_CA_CERT` | Pfad zum benutzerdefinierten CA-Zertifikat für Elasticsearch SSL/TLS | NEIN |\n\n### Lokale Entwicklung\n\n> \\[!NOTE] Wenn Sie den MCP-Server ändern oder erweitern möchten, befolgen Sie diese lokalen Entwicklungsschritte.\n\n1. **Verwenden Sie die richtige Node.js-Version**\n\n ```bash\n nvm use\n ```\n\n2. **Abhängigkeiten installieren**\n\n ```bash\n npm install\n ```\n\n3. **Erstellen des Projekts**\n\n ```bash\n npm run build\n ```\n\n4. **Lokal in der Claude Desktop App ausführen**\n\n * Öffnen Sie **die Claude Desktop App**\n * Gehen Sie zu **Einstellungen > Entwickler > MCP-Server**\n * Klicken Sie auf `Edit Config` und fügen Sie einen neuen MCP-Server mit der folgenden Konfiguration hinzu:\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server-local\": {\n \"command\": \"node\",\n \"args\": [\n \"/path/to/your/project/dist/index.js\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n5. **Debuggen mit MCP Inspector**\n\n ```bash\n ES_URL=your-elasticsearch-url ES_API_KEY=your-api-key npm run inspector\n ```\n\n Dadurch wird der MCP Inspector gestartet, mit dem Sie Anfragen debuggen und analysieren können. Folgendes sollte angezeigt werden:\n\n ```bash\n Starting MCP inspector...\n Proxy server listening on port 3000\n\n 🔍 MCP Inspector is up and running at http://localhost:5173 🚀\n ```\n\n## Beitragen\n\nWir freuen uns über Beiträge aus der Community! Weitere Informationen dazu, wie Sie beitragen können, finden Sie in [den Richtlinien für Beiträge](/docs/CONTRIBUTING.md) .\n\n## Beispielfragen\n\n> \\[!TIP] Hier sind einige Abfragen in natürlicher Sprache, die Sie mit Ihrem MCP-Client ausprobieren können.\n\n* „Welche Indizes habe ich in meinem Elasticsearch-Cluster?“\n* „Zeigen Sie mir die Feldzuordnungen für den Index ‚Produkte‘.“\n* „Finden Sie alle Bestellungen über 500 $ vom letzten Monat.“\n* „Welche Produkte haben die meisten 5-Sterne-Bewertungen erhalten?“\n\n## Wie es funktioniert\n\n1. Der MCP-Client analysiert Ihre Anfrage und ermittelt, welche Elasticsearch-Operationen erforderlich sind.\n2. Der MCP-Server führt diese Vorgänge aus (Auflisten von Indizes, Abrufen von Zuordnungen, Durchführen von Suchvorgängen).\n3. Der MCP-Client verarbeitet die Ergebnisse und präsentiert sie in einem benutzerfreundlichen Format.\n\n## Bewährte Sicherheitspraktiken\n\n> \\[!WARNING] Vermeiden Sie die Verwendung von Clusteradministratorberechtigungen. Erstellen Sie dedizierte API-Schlüssel mit begrenztem Umfang und wenden Sie eine differenzierte Zugriffssteuerung auf Indexebene an, um unbefugten Datenzugriff zu verhindern.\n\nSie können einen dedizierten Elasticsearch-API-Schlüssel mit minimalen Berechtigungen erstellen, um den Zugriff auf Ihre Daten zu kontrollieren:\n\n```\nPOST /_security/api_key\n{\n \"name\": \"es-mcp-server-access\",\n \"role_descriptors\": {\n \"mcp_server_role\": {\n \"cluster\": [\n \"monitor\"\n ],\n \"indices\": [\n {\n \"names\": [\n \"index-1\",\n \"index-2\",\n \"index-pattern-*\"\n ],\n \"privileges\": [\n \"read\",\n \"view_index_metadata\"\n ]\n }\n ]\n }\n }\n}\n```\n\n## Lizenz\n\nDieses Projekt ist unter der Apache-Lizenz 2.0 lizenziert.\n\n## Fehlerbehebung\n\n* Stellen Sie sicher, dass Ihre MCP-Konfiguration korrekt ist.\n* Stellen Sie sicher, dass Ihre Elasticsearch-URL von Ihrem Computer aus zugänglich ist.\n* Überprüfen Sie, ob Ihre Authentifizierungsdaten (API-Schlüssel oder Benutzername/Passwort) über die erforderlichen Berechtigungen verfügen.\n* Wenn Sie SSL/TLS mit einer benutzerdefinierten Zertifizierungsstelle verwenden, überprüfen Sie, ob der Zertifikatspfad korrekt ist und die Datei lesbar ist.\n* Suchen Sie in der Terminalausgabe nach Fehlermeldungen.\n\nWenn Sie auf Probleme stoßen, können Sie gerne ein Problem im GitHub-Repository öffnen.","German","tag","de-DE",{"_27":39,"_31":43,"_36":44},{"_29":40,"_31":41,"_33":42},"Connects Claude and other MCP clients to Elasticsearch data, allowing users to interact with their Elasticsearch indices through natural language conversations.","Elasticsearch MCP Server","# Elasticsearch MCP Server\n\nThis repository contains experimental features intended for research and evaluation and are not production-ready.\n\nConnect to your Elasticsearch data directly from any MCP Client (like Claude Desktop) using the Model Context Protocol (MCP).\n\nThis server connects agents to your Elasticsearch data using the Model Context Protocol. It allows you to interact with your Elasticsearch indices through natural language conversations.\n\n\n $\"Elasticsearch$ \n\n\n## Available Tools\n\n* `list_indices`: List all available Elasticsearch indices\n* `get_mappings`: Get field mappings for a specific Elasticsearch index\n* `search`: Perform an Elasticsearch search with the provided query DSL\n* `get_shards`: Get shard information for all or specific indices\n\n## Prerequisites\n\n* An Elasticsearch instance\n* Elasticsearch authentication credentials (API key or username/password)\n* MCP Client (e.g. Claude Desktop)\n\n## Demo\n\nhttps://github.com/user-attachments/assets/5dd292e1-a728-4ca7-8f01-1380d1bebe0c\n\n## Installation & Setup\n\n### Using the Published NPM Package\n\n> [!TIP]\n> The easiest way to use Elasticsearch MCP Server is through the published npm package.\n\n1. **Configure MCP Client**\n - Open your MCP Client. See the [list of MCP Clients](https://modelcontextprotocol.io/clients), here we are configuring Claude Desktop.\n - Go to **Settings > Developer > MCP Servers**\n - Click `Edit Config` and add a new MCP Server with the following configuration:\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@elastic/mcp-server-elasticsearch\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n2. **Start a Conversation**\n - Open a new conversation in your MCP Client\n - The MCP server should connect automatically\n - You can now ask questions about your Elasticsearch data\n\n### Configuration Options\n\nThe Elasticsearch MCP Server supports configuration options to connect to your Elasticsearch:\n\n> [!NOTE]\n> You must provide either an API key or both username and password for authentication.\n\n\n| Environment Variable | Description | Required |\n|---------------------|-------------|----------|\n| `ES_URL` | Your Elasticsearch instance URL | Yes |\n| `ES_API_KEY` | Elasticsearch API key for authentication | No |\n| `ES_USERNAME` | Elasticsearch username for basic authentication | No |\n| `ES_PASSWORD` | Elasticsearch password for basic authentication | No |\n| `ES_CA_CERT` | Path to custom CA certificate for Elasticsearch SSL/TLS | No |\n\n\n### Developing Locally\n\n> [!NOTE]\n> If you want to modify or extend the MCP Server, follow these local development steps.\n\n1. **Use the correct Node.js version**\n ```bash\n nvm use\n ```\n\n2. **Install Dependencies**\n ```bash\n npm install\n ```\n\n3. **Build the Project**\n ```bash\n npm run build\n ```\n\n4. **Run locally in Claude Desktop App**\n - Open **Claude Desktop App**\n - Go to **Settings > Developer > MCP Servers**\n - Click `Edit Config` and add a new MCP Server with the following configuration:\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server-local\": {\n \"command\": \"node\",\n \"args\": [\n \"/path/to/your/project/dist/index.js\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n5. **Debugging with MCP Inspector**\n ```bash\n ES_URL=your-elasticsearch-url ES_API_KEY=your-api-key npm run inspector\n ```\n\n This will start the MCP Inspector, allowing you to debug and analyze requests. You should see:\n\n ```bash\n Starting MCP inspector...\n Proxy server listening on port 3000\n\n 🔍 MCP Inspector is up and running at http://localhost:5173 🚀\n ```\n\n## Contributing\n\nWe welcome contributions from the community! For details on how to contribute, please see [Contributing Guidelines](/docs/CONTRIBUTING.md).\n\n## Example Questions\n\n> [!TIP]\n> Here are some natural language queries you can try with your MCP Client.\n\n* \"What indices do I have in my Elasticsearch cluster?\"\n* \"Show me the field mappings for the 'products' index.\"\n* \"Find all orders over $500 from last month.\"\n* \"Which products received the most 5-star reviews?\"\n\n## How It Works\n\n1. The MCP Client analyzes your request and determines which Elasticsearch operations are needed.\n2. The MCP server carries out these operations (listing indices, fetching mappings, performing searches).\n3. The MCP Client processes the results and presents them in a user-friendly format.\n\n## Security Best Practices\n\n> [!WARNING]\n> Avoid using cluster-admin privileges. Create dedicated API keys with limited scope and apply fine-grained access control at the index level to prevent unauthorized data access.\n\nYou can create a dedicated Elasticsearch API key with minimal permissions to control access to your data:\n\n```\nPOST /_security/api_key\n{\n \"name\": \"es-mcp-server-access\",\n \"role_descriptors\": {\n \"mcp_server_role\": {\n \"cluster\": [\n \"monitor\"\n ],\n \"indices\": [\n {\n \"names\": [\n \"index-1\",\n \"index-2\",\n \"index-pattern-*\"\n ],\n \"privileges\": [\n \"read\",\n \"view_index_metadata\"\n ]\n }\n ]\n }\n }\n}\n```\n\n## License\n\nThis project is licensed under the Apache License 2.0.\n\n## Troubleshooting\n\n* Ensure your MCP configuration is correct.\n* Verify that your Elasticsearch URL is accessible from your machine.\n* Check that your authentication credentials (API key or username/password) have the necessary permissions.\n* If using SSL/TLS with a custom CA, verify that the certificate path is correct and the file is readable.\n* Look at the terminal output for error messages.\n\nIf you encounter issues, feel free to open an issue on the GitHub repository.\n","English","en-US",{"_27":46,"_31":50,"_36":51},{"_29":47,"_31":48,"_33":49},"Conecta a Claude y otros clientes de MCP con los datos de Elasticsearch, lo que permite a los usuarios interactuar con sus índices de Elasticsearch a través de conversaciones en lenguaje natural.","Servidor MCP de Elasticsearch","# Servidor MCP de Elasticsearch\n\nEste repositorio contiene características experimentales destinadas a la investigación y la evaluación y no están listas para producción.\n\nConéctese a sus datos de Elasticsearch directamente desde cualquier cliente MCP (como Claude Desktop) utilizando el Protocolo de contexto de modelo (MCP).\n\nEste servidor conecta a los agentes con sus datos de Elasticsearch mediante el Protocolo de Contexto de Modelo. Le permite interactuar con sus índices de Elasticsearch mediante conversaciones en lenguaje natural.\n\n## Herramientas disponibles\n\n* `list_indices` : Lista todos los índices de Elasticsearch disponibles\n* `get_mappings` : obtiene asignaciones de campos para un índice Elasticsearch específico\n* `search` : Realiza una búsqueda de Elasticsearch con la consulta DSL proporcionada\n* `get_shards` : Obtener información de fragmentos para todos los índices o para índices específicos\n\n## Prerrequisitos\n\n* Una instancia de Elasticsearch\n* Credenciales de autenticación de Elasticsearch (clave API o nombre de usuario/contraseña)\n* Cliente MCP (por ejemplo, Claude Desktop)\n\n## Manifestación\n\n\n\n## Instalación y configuración\n\n### Uso del paquete NPM publicado\n\n> \\[!TIP] La forma más sencilla de utilizar Elasticsearch MCP Server es a través del paquete npm publicado.\n\n1. **Configurar el cliente MCP**\n\n * Abra su cliente MCP. Consulte la [lista de clientes MCP](https://modelcontextprotocol.io/clients) . Aquí estamos configurando Claude Desktop.\n * Vaya a **Configuración > Desarrollador > Servidores MCP**\n * Haga clic `Edit Config` y agregue un nuevo servidor MCP con la siguiente configuración:\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@elastic/mcp-server-elasticsearch\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n2. **Iniciar una conversación**\n\n * Abra una nueva conversación en su cliente MCP\n * El servidor MCP debería conectarse automáticamente\n * Ahora puedes hacer preguntas sobre tus datos de Elasticsearch\n\n### Opciones de configuración\n\nEl servidor MCP de Elasticsearch admite opciones de configuración para conectarse a su Elasticsearch:\n\n> \\[!NOTA] Debe proporcionar una clave API o un nombre de usuario y una contraseña para la autenticación.\n\n| Variable de entorno | Descripción | Requerido |\n| ------------------- | --------------------------------------------------------------- | --------- |\n| `ES_URL` | La URL de su instancia de Elasticsearch | Sí |\n| `ES_API_KEY` | Clave API de Elasticsearch para autenticación | No |\n| `ES_USERNAME` | Nombre de usuario de Elasticsearch para autenticación básica | No |\n| `ES_PASSWORD` | Contraseña de Elasticsearch para autenticación básica | No |\n| `ES_CA_CERT` | Ruta al certificado CA personalizado para Elasticsearch SSL/TLS | No |\n\n### Desarrollo local\n\n> \\[!NOTA] Si desea modificar o ampliar el servidor MCP, siga estos pasos de desarrollo local.\n\n1. **Utilice la versión correcta de Node.js**\n\n ```bash\n nvm use\n ```\n\n2. **Instalar dependencias**\n\n ```bash\n npm install\n ```\n\n3. **Construir el proyecto**\n\n ```bash\n npm run build\n ```\n\n4. **Ejecutar localmente en la aplicación de escritorio Claude**\n\n * Abra **la aplicación de escritorio Claude**\n * Vaya a **Configuración > Desarrollador > Servidores MCP**\n * Haga clic `Edit Config` y agregue un nuevo servidor MCP con la siguiente configuración:\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server-local\": {\n \"command\": \"node\",\n \"args\": [\n \"/path/to/your/project/dist/index.js\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n5. **Depuración con MCP Inspector**\n\n ```bash\n ES_URL=your-elasticsearch-url ES_API_KEY=your-api-key npm run inspector\n ```\n\n Esto iniciará el Inspector MCP, lo que le permitirá depurar y analizar solicitudes. Debería ver lo siguiente:\n\n ```bash\n Starting MCP inspector...\n Proxy server listening on port 3000\n\n 🔍 MCP Inspector is up and running at http://localhost:5173 🚀\n ```\n\n## Contribuyendo\n\n¡Agradecemos las contribuciones de la comunidad! Para más información sobre cómo contribuir, consulta [las Pautas de Contribución](/docs/CONTRIBUTING.md) .\n\n## Preguntas de ejemplo\n\n> \\[!TIP] Aquí hay algunas consultas en lenguaje natural que puedes probar con tu cliente MCP.\n\n* \"¿Qué índices tengo en mi clúster Elasticsearch?\"\n* \"Muéstrame las asignaciones de campos para el índice 'productos'\".\n* \"Encuentre todos los pedidos superiores a $500 del mes pasado\".\n* \"¿Qué productos recibieron más reseñas de 5 estrellas?\"\n\n## Cómo funciona\n\n1. El cliente MCP analiza su solicitud y determina qué operaciones de Elasticsearch son necesarias.\n2. El servidor MCP lleva a cabo estas operaciones (enumerar índices, obtener asignaciones, realizar búsquedas).\n3. El cliente MCP procesa los resultados y los presenta en un formato fácil de usar.\n\n## Mejores prácticas de seguridad\n\n> \\[!ADVERTENCIA] Evite usar privilegios de administrador del clúster. Cree claves de API dedicadas con alcance limitado y aplique un control de acceso preciso a nivel de índice para evitar el acceso no autorizado a los datos.\n\nPuede crear una clave API de Elasticsearch dedicada con permisos mínimos para controlar el acceso a sus datos:\n\n```\nPOST /_security/api_key\n{\n \"name\": \"es-mcp-server-access\",\n \"role_descriptors\": {\n \"mcp_server_role\": {\n \"cluster\": [\n \"monitor\"\n ],\n \"indices\": [\n {\n \"names\": [\n \"index-1\",\n \"index-2\",\n \"index-pattern-*\"\n ],\n \"privileges\": [\n \"read\",\n \"view_index_metadata\"\n ]\n }\n ]\n }\n }\n}\n```\n\n## Licencia\n\nEste proyecto está licenciado bajo la Licencia Apache 2.0.\n\n## Solución de problemas\n\n* Asegúrese de que la configuración de su MCP sea correcta.\n* Verifique que su URL de Elasticsearch sea accesible desde su máquina.\n* Verifique que sus credenciales de autenticación (clave API o nombre de usuario/contraseña) tengan los permisos necesarios.\n* Si usa SSL/TLS con una CA personalizada, verifique que la ruta del certificado sea correcta y que el archivo sea legible.\n* Observe la salida del terminal para ver si hay mensajes de error.\n\nSi encuentra problemas, no dude en abrir un problema en el repositorio de GitHub.","Spanish","es-ES",{"_27":53,"_31":57,"_36":58},{"_29":54,"_31":55,"_33":56},"Claude およびその他の MCP クライアントを Elasticsearch データに接続し、ユーザーが自然言語の会話を通じて Elasticsearch インデックスを操作できるようにします。","Elasticsearch MCP サーバー","# Elasticsearch MCP サーバー\n\nこのリポジトリには、研究と評価を目的とした実験的な機能が含まれており、実稼働には対応していません。\n\nモデルコンテキストプロトコル (MCP) を使用して、任意の MCP クライアント (Claude Desktop など) から Elasticsearch データに直接接続します。\n\nこのサーバーは、モデルコンテキストプロトコルを使用してエージェントをElasticsearchデータに接続します。これにより、自然言語による会話を通じてElasticsearchインデックスと対話できるようになります。\n\n## 利用可能なツール\n\n* `list_indices` : 利用可能なすべてのElasticsearchインデックスを一覧表示する\n* `get_mappings` : 特定のElasticsearchインデックスのフィールドマッピングを取得する\n* `search` : 提供されたクエリDSLを使用してElasticsearch検索を実行する\n* `get_shards` : すべてまたは特定のインデックスのシャード情報を取得する\n\n## 前提条件\n\n* Elasticsearchインスタンス\n* Elasticsearch 認証資格情報 (API キーまたはユーザー名/パスワード)\n* MCP クライアント (例: Claude Desktop)\n\n## デモ\n\n\n\n## インストールとセットアップ\n\n### 公開されたNPMパッケージの使用\n\n> \\[!TIP] Elasticsearch MCP Server を使用する最も簡単な方法は、公開されている npm パッケージを使用することです。\n\n1. **MCPクライアントの設定**\n\n * MCPクライアントを開きます。MCP[クライアントのリスト](https://modelcontextprotocol.io/clients)を確認し、ここでClaude Desktopを設定します。\n * **設定 > 開発者 > MCP サーバー**に移動します\n * `Edit Config`をクリックし、次の設定で新しい MCP サーバーを追加します。\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@elastic/mcp-server-elasticsearch\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n2. **会話を始める**\n\n * MCPクライアントで新しい会話を開きます\n * MCPサーバーは自動的に接続されます\n * Elasticsearchデータについて質問できるようになりました\n\n### 設定オプション\n\nElasticsearch MCP サーバーは、Elasticsearch に接続するための構成オプションをサポートしています。\n\n> \\[!NOTE] 認証には、API キーまたはユーザー名とパスワードの両方を指定する必要があります。\n\n| 環境変数 | 説明 | 必須 |\n| ------------- | -------------------------------------- | --- |\n| `ES_URL` | ElasticsearchインスタンスのURL | はい |\n| `ES_API_KEY` | 認証用のElasticsearch APIキー | いいえ |\n| `ES_USERNAME` | 基本認証用のElasticsearchユーザー名 | いいえ |\n| `ES_PASSWORD` | 基本認証用のElasticsearchパスワード | いいえ |\n| `ES_CA_CERT` | Elasticsearch SSL/TLS のカスタム CA 証明書へのパス | いいえ |\n\n### 地域開発\n\n> \\[!NOTE] MCP サーバーを変更または拡張する場合は、次のローカル開発手順に従ってください。\n\n1. **正しいNode.jsバージョンを使用する**\n\n ```bash\n nvm use\n ```\n\n2. **依存関係をインストールする**\n\n ```bash\n npm install\n ```\n\n3. **プロジェクトを構築する**\n\n ```bash\n npm run build\n ```\n\n4. **Claudeデスクトップアプリでローカルに実行**\n\n * **Claudeデスクトップアプリ**を開く\n * **設定 > 開発者 > MCP サーバー**に移動します\n * `Edit Config`をクリックし、次の設定で新しい MCP サーバーを追加します。\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server-local\": {\n \"command\": \"node\",\n \"args\": [\n \"/path/to/your/project/dist/index.js\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n5. **MCP Inspectorによるデバッグ**\n\n ```bash\n ES_URL=your-elasticsearch-url ES_API_KEY=your-api-key npm run inspector\n ```\n\n MCP Inspectorが起動し、リクエストのデバッグと分析が可能になります。以下の画面が表示されます。\n\n ```bash\n Starting MCP inspector...\n Proxy server listening on port 3000\n\n 🔍 MCP Inspector is up and running at http://localhost:5173 🚀\n ```\n\n## 貢献\n\nコミュニティからの貢献を歓迎します。貢献方法の詳細については、[貢献ガイドライン](/docs/CONTRIBUTING.md)をご覧ください。\n\n## 例題\n\n> \\[!TIP] MCP クライアントで試すことができる自然言語クエリをいくつか示します。\n\n* 「Elasticsearch クラスターにはどのようなインデックスがありますか?」\n* 「「製品」インデックスのフィールドマッピングを表示します。」\n* 「先月の 500 ドルを超えるすべての注文を検索します。」\n* 「5 つ星のレビューを最も多く獲得した製品はどれですか?」\n\n## 仕組み\n\n1. MCP クライアントはリクエストを分析し、必要な Elasticsearch 操作を決定します。\n2. MCP サーバーはこれらの操作 (インデックスの一覧表示、マッピングの取得、検索の実行) を実行します。\n3. MCP クライアントは結果を処理し、ユーザーフレンドリーな形式で表示します。\n\n## セキュリティのベストプラクティス\n\n> \\[!WARNING] クラスター管理者権限の使用は避けてください。スコープを制限した専用のAPIキーを作成し、インデックスレベルできめ細かなアクセス制御を適用して、不正なデータアクセスを防止してください。\n\nデータへのアクセスを制御するために、最小限の権限を持つ専用の Elasticsearch API キーを作成できます。\n\n```\nPOST /_security/api_key\n{\n \"name\": \"es-mcp-server-access\",\n \"role_descriptors\": {\n \"mcp_server_role\": {\n \"cluster\": [\n \"monitor\"\n ],\n \"indices\": [\n {\n \"names\": [\n \"index-1\",\n \"index-2\",\n \"index-pattern-*\"\n ],\n \"privileges\": [\n \"read\",\n \"view_index_metadata\"\n ]\n }\n ]\n }\n }\n}\n```\n\n## ライセンス\n\nこのプロジェクトは、Apache License 2.0 に基づいてライセンスされています。\n\n## トラブルシューティング\n\n* MCP 構成が正しいことを確認してください。\n* Elasticsearch URL がマシンからアクセスできることを確認します。\n* 認証資格情報 (API キーまたはユーザー名/パスワード) に必要な権限があることを確認します。\n* カスタム CA で SSL/TLS を使用する場合は、証明書パスが正しいことと、ファイルが読み取り可能であることを確認します。\n* エラーメッセージのターミナル出力を確認します。\n\n問題が発生した場合は、お気軽に GitHub リポジトリで問題を報告してください。","Japanese","ja-JP",{"_27":60,"_31":64,"_36":65},{"_29":61,"_31":62,"_33":63},"Claude와 다른 MCP 클라이언트를 Elasticsearch 데이터에 연결하여 사용자가 자연어 대화를 통해 Elasticsearch 인덱스와 상호 작용할 수 있도록 합니다.","Elasticsearch MCP 서버","# Elasticsearch MCP 서버\n\n이 저장소에는 연구 및 평가를 위한 실험적 기능이 포함되어 있으며, 아직 실제 운영에 적용할 준비가 되지 않았습니다.\n\nModel Context Protocol(MCP)을 사용하여 모든 MCP 클라이언트(예: Claude Desktop)에서 Elasticsearch 데이터에 직접 연결합니다.\n\n이 서버는 모델 컨텍스트 프로토콜(Model Context Protocol)을 사용하여 에이전트를 Elasticsearch 데이터에 연결합니다. 자연어 대화를 통해 Elasticsearch 인덱스와 상호 작용할 수 있습니다.\n\n## 사용 가능한 도구\n\n* `list_indices` : 사용 가능한 모든 Elasticsearch 인덱스를 나열합니다.\n* `get_mappings` : 특정 Elasticsearch 인덱스에 대한 필드 매핑을 가져옵니다.\n* `search` : 제공된 쿼리 DSL로 Elasticsearch 검색을 수행합니다.\n* `get_shards` : 모든 인덱스 또는 특정 인덱스에 대한 샤드 정보를 가져옵니다.\n\n## 필수 조건\n\n* Elasticsearch 인스턴스\n* Elasticsearch 인증 자격 증명(API 키 또는 사용자 이름/비밀번호)\n* MCP 클라이언트(예: Claude Desktop)\n\n## 데모\n\n\n\n## 설치 및 설정\n\n### 게시된 NPM 패키지 사용\n\n> \\[!TIP] Elasticsearch MCP 서버를 사용하는 가장 쉬운 방법은 게시된 npm 패키지를 사용하는 것입니다.\n\n1. **MCP 클라이언트 구성**\n\n * MCP 클라이언트를 엽니다. [MCP 클라이언트 목록을](https://modelcontextprotocol.io/clients) 확인하세요. 여기서는 Claude Desktop을 구성하고 있습니다.\n * **설정 > 개발자 > MCP 서버** 로 이동하세요.\n * `Edit Config` 클릭하고 다음 구성으로 새 MCP 서버를 추가합니다.\n\n 지엑스피1\n\n2. **대화 시작하기**\n\n * MCP 클라이언트에서 새 대화를 엽니다.\n * MCP 서버는 자동으로 연결되어야 합니다.\n * 이제 Elasticsearch 데이터에 대해 질문할 수 있습니다.\n\n### 구성 옵션\n\nElasticsearch MCP 서버는 Elasticsearch에 연결하기 위한 구성 옵션을 지원합니다.\n\n> \\[!NOTE] 인증을 위해서는 API 키 또는 사용자 이름과 비밀번호를 모두 제공해야 합니다.\n\n| 환경 변수 | 설명 | 필수의 |\n| ------------- | ------------------------------------------ | --- |\n| `ES_URL` | Elasticsearch 인스턴스 URL | 예 |\n| `ES_API_KEY` | 인증을 위한 Elasticsearch API 키 | 아니요 |\n| `ES_USERNAME` | 기본 인증을 위한 Elasticsearch 사용자 이름 | 아니요 |\n| `ES_PASSWORD` | 기본 인증을 위한 Elasticsearch 비밀번호 | 아니요 |\n| `ES_CA_CERT` | Elasticsearch SSL/TLS에 대한 사용자 정의 CA 인증서 경로 | 아니요 |\n\n### 지역적으로 개발하다\n\n> \\[!NOTE] MCP 서버를 수정하거나 확장하려면 다음 로컬 개발 단계를 따르세요.\n\n1. **올바른 Node.js 버전을 사용하세요**\n\n ```bash\n nvm use\n ```\n\n2. **종속성 설치**\n\n ```bash\n npm install\n ```\n\n3. **프로젝트 빌드**\n\n ```bash\n npm run build\n ```\n\n4. **Claude Desktop App에서 로컬로 실행**\n\n * **Claude 데스크톱 앱** 열기\n * **설정 > 개발자 > MCP 서버** 로 이동하세요.\n * `Edit Config` 클릭하고 다음 구성으로 새 MCP 서버를 추가합니다.\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server-local\": {\n \"command\": \"node\",\n \"args\": [\n \"/path/to/your/project/dist/index.js\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n5. **MCP Inspector를 사용한 디버깅**\n\n ```bash\n ES_URL=your-elasticsearch-url ES_API_KEY=your-api-key npm run inspector\n ```\n\n 그러면 MCP Inspector가 시작되어 요청을 디버깅하고 분석할 수 있습니다. 다음이 표시됩니다.\n\n ```bash\n Starting MCP inspector...\n Proxy server listening on port 3000\n\n 🔍 MCP Inspector is up and running at http://localhost:5173 🚀\n ```\n\n## 기여하다\n\n커뮤니티 여러분의 참여를 환영합니다! 참여 방법에 대한 자세한 내용은 ['참여 가이드라인'을](/docs/CONTRIBUTING.md) 참조하세요.\n\n## 예시 질문\n\n> \\[!TIP] MCP 클라이언트에서 시도할 수 있는 자연어 쿼리는 다음과 같습니다.\n\n* \"Elasticsearch 클러스터에는 어떤 인덱스가 있나요?\"\n* '제품' 인덱스에 대한 필드 매핑을 보여주세요.\n* \"지난달 500달러 이상 주문한 모든 주문을 찾으세요.\"\n* \"어떤 제품이 5점 만점에 가장 많은 리뷰를 받았나요?\"\n\n## 작동 원리\n\n1. MCP 클라이언트는 귀하의 요청을 분석하고 어떤 Elasticsearch 작업이 필요한지 결정합니다.\n2. MCP 서버는 다음과 같은 작업(인덱스 나열, 매핑 가져오기, 검색 수행)을 수행합니다.\n3. MCP 클라이언트는 결과를 처리하여 사용자 친화적인 형식으로 표시합니다.\n\n## 보안 모범 사례\n\n> \\[!경고] 클러스터 관리자 권한 사용을 피하세요. 제한된 범위의 전용 API 키를 생성하고 인덱스 수준에서 세분화된 액세스 제어를 적용하여 무단 데이터 액세스를 방지하세요.\n\n최소한의 권한으로 전용 Elasticsearch API 키를 만들어 데이터 액세스를 제어할 수 있습니다.\n\n```\nPOST /_security/api_key\n{\n \"name\": \"es-mcp-server-access\",\n \"role_descriptors\": {\n \"mcp_server_role\": {\n \"cluster\": [\n \"monitor\"\n ],\n \"indices\": [\n {\n \"names\": [\n \"index-1\",\n \"index-2\",\n \"index-pattern-*\"\n ],\n \"privileges\": [\n \"read\",\n \"view_index_metadata\"\n ]\n }\n ]\n }\n }\n}\n```\n\n## 특허\n\n이 프로젝트는 Apache License 2.0에 따라 라이선스가 부여되었습니다.\n\n## 문제 해결\n\n* MCP 구성이 올바른지 확인하세요.\n* 귀하의 컴퓨터에서 Elasticsearch URL에 접근할 수 있는지 확인하세요.\n* 인증 자격 증명(API 키 또는 사용자 이름/비밀번호)에 필요한 권한이 있는지 확인하세요.\n* 사용자 지정 CA와 함께 SSL/TLS를 사용하는 경우 인증서 경로가 올바르고 파일을 읽을 수 있는지 확인하세요.\n* 오류 메시지는 터미널 출력을 확인하세요.\n\n문제가 발생하면 GitHub 저장소에서 문제를 제기해 주시기 바랍니다.","Korean","ko-KR",{"_27":67,"_31":71,"_36":72},{"_29":68,"_31":69,"_33":70},"Подключает Claude и других клиентов MCP к данным Elasticsearch, позволяя пользователям взаимодействовать со своими индексами Elasticsearch посредством общения на естественном языке.","Сервер Elasticsearch MCP","# Сервер Elasticsearch MCP\n\nЭтот репозиторий содержит экспериментальные функции, предназначенные для исследований и оценки и не готовые к использованию в производстве.\n\nПодключитесь к данным Elasticsearch напрямую из любого клиента MCP (например, Claude Desktop) с помощью протокола контекста модели (MCP).\n\nЭтот сервер подключает агентов к вашим данным Elasticsearch с помощью Model Context Protocol. Он позволяет вам взаимодействовать с вашими индексами Elasticsearch посредством разговоров на естественном языке.\n\n## Доступные инструменты\n\n* `list_indices` : Список всех доступных индексов Elasticsearch\n* `get_mappings` : Получить сопоставления полей для определенного индекса Elasticsearch\n* `search` : выполнить поиск Elasticsearch с предоставленным запросом DSL\n* `get_shards` : Получить информацию о шардах для всех или определенных индексов\n\n## Предпосылки\n\n* Экземпляр Elasticsearch\n* Учетные данные аутентификации Elasticsearch (ключ API или имя пользователя/пароль)\n* Клиент MCP (например, Claude Desktop)\n\n## Демо\n\n\n\n## Установка и настройка\n\n### Использование опубликованного пакета NPM\n\n> \\[!СОВЕТ] Самый простой способ использовать сервер Elasticsearch MCP — через опубликованный пакет npm.\n\n1. **Настроить MCP-клиент**\n\n * Откройте ваш MCP Client. Посмотрите [список MCP Clients](https://modelcontextprotocol.io/clients) , здесь мы настраиваем Claude Desktop.\n * Перейдите в **Настройки > Разработчик > Серверы MCP.**\n * Нажмите `Edit Config` и добавьте новый сервер MCP со следующей конфигурацией:\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@elastic/mcp-server-elasticsearch\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n2. **Начать разговор**\n\n * Откройте новый разговор в вашем MCP Client\n * Сервер MCP должен подключиться автоматически.\n * Теперь вы можете задавать вопросы о своих данных Elasticsearch\n\n### Параметры конфигурации\n\nСервер Elasticsearch MCP поддерживает параметры конфигурации для подключения к Elasticsearch:\n\n> \\[!ПРИМЕЧАНИЕ] Для аутентификации необходимо предоставить либо ключ API, либо имя пользователя и пароль.\n\n| Переменная среды | Описание | Необходимый |\n| ---------------- | ----------------------------------------------------------------- | ----------- |\n| `ES_URL` | URL вашего экземпляра Elasticsearch | Да |\n| `ES_API_KEY` | Ключ API Elasticsearch для аутентификации | Нет |\n| `ES_USERNAME` | Имя пользователя Elasticsearch для базовой аутентификации | Нет |\n| `ES_PASSWORD` | Пароль Elasticsearch для базовой аутентификации | Нет |\n| `ES_CA_CERT` | Путь к пользовательскому сертификату CA для Elasticsearch SSL/TLS | Нет |\n\n### Развитие на местном уровне\n\n> \\[!ПРИМЕЧАНИЕ] Если вы хотите изменить или расширить сервер MCP, следуйте этим шагам локальной разработки.\n\n1. **Используйте правильную версию Node.js**\n\n ```bash\n nvm use\n ```\n\n2. **Установить зависимости**\n\n ```bash\n npm install\n ```\n\n3. **Построить проект**\n\n ```bash\n npm run build\n ```\n\n4. **Запустить локально в приложении Claude Desktop**\n\n * Открыть **приложение Claude для ПК**\n * Перейдите в **Настройки > Разработчик > Серверы MCP.**\n * Нажмите `Edit Config` и добавьте новый сервер MCP со следующей конфигурацией:\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server-local\": {\n \"command\": \"node\",\n \"args\": [\n \"/path/to/your/project/dist/index.js\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n5. **Отладка с помощью MCP Inspector**\n\n ```bash\n ES_URL=your-elasticsearch-url ES_API_KEY=your-api-key npm run inspector\n ```\n\n Это запустит MCP Inspector, позволяющий вам отлаживать и анализировать запросы. Вы должны увидеть:\n\n ```bash\n Starting MCP inspector...\n Proxy server listening on port 3000\n\n 🔍 MCP Inspector is up and running at http://localhost:5173 🚀\n ```\n\n## Внося вклад\n\nМы приветствуем вклады от сообщества! Подробности о том, как внести вклад, см. [в Руководстве по внесению вкладов](/docs/CONTRIBUTING.md) .\n\n## Примеры вопросов\n\n> \\[!СОВЕТ] Вот несколько запросов на естественном языке, которые вы можете попробовать выполнить с помощью своего клиента MCP.\n\n* «Какие индексы есть в моем кластере Elasticsearch?»\n* «Покажите мне сопоставления полей для индекса «продукты»».\n* «Найти все заказы на сумму более 500 долларов за прошлый месяц».\n* «Какие продукты получили наибольшее количество 5-звездочных отзывов?»\n\n## Как это работает\n\n1. Клиент MCP анализирует ваш запрос и определяет, какие операции Elasticsearch необходимы.\n2. Сервер MCP выполняет эти операции (перечисление индексов, выборку сопоставлений, выполнение поиска).\n3. Клиент MCP обрабатывает результаты и представляет их в удобном для пользователя формате.\n\n## Лучшие практики безопасности\n\n> \\[!WARNING] Избегайте использования привилегий администратора кластера. Создавайте выделенные ключи API с ограниченной областью действия и применяйте детальный контроль доступа на уровне индекса, чтобы предотвратить несанкционированный доступ к данным.\n\nВы можете создать специальный ключ API Elasticsearch с минимальными правами доступа для управления доступом к вашим данным:\n\n```\nPOST /_security/api_key\n{\n \"name\": \"es-mcp-server-access\",\n \"role_descriptors\": {\n \"mcp_server_role\": {\n \"cluster\": [\n \"monitor\"\n ],\n \"indices\": [\n {\n \"names\": [\n \"index-1\",\n \"index-2\",\n \"index-pattern-*\"\n ],\n \"privileges\": [\n \"read\",\n \"view_index_metadata\"\n ]\n }\n ]\n }\n }\n}\n```\n\n## Лицензия\n\nДанный проект лицензирован по лицензии Apache License 2.0.\n\n## Поиск неисправностей\n\n* Убедитесь, что конфигурация вашего MCP правильная.\n* Убедитесь, что URL-адрес Elasticsearch доступен с вашего компьютера.\n* Убедитесь, что ваши учетные данные аутентификации (ключ API или имя пользователя/пароль) имеют необходимые разрешения.\n* При использовании SSL/TLS с пользовательским центром сертификации убедитесь, что путь к сертификату указан правильно и файл доступен для чтения.\n* Проверьте вывод терминала на наличие сообщений об ошибках.\n\nЕсли у вас возникли проблемы, смело сообщайте о них в репозитории GitHub.","Russian","ru-RU",{"_27":74,"_31":78,"_36":79},{"_29":75,"_31":76,"_33":77},"将 Claude 和其他 MCP 客户端连接到 Elasticsearch 数据，允许用户通过自然语言对话与他们的 Elasticsearch 索引进行交互。","Elasticsearch MCP 服务器","# Elasticsearch MCP 服务器\n\n该存储库包含用于研究和评估的实验性功能，尚不适用于生产。\n\n使用模型上下文协议 (MCP) 直接从任何 MCP 客户端（如 Claude Desktop）连接到您的 Elasticsearch 数据。\n\n该服务器使用模型上下文协议 (MCP) 将代理连接到您的 Elasticsearch 数据。它允许您通过自然语言对话与您的 Elasticsearch 索引进行交互。\n\n## 可用工具\n\n* `list_indices` ：列出所有可用的 Elasticsearch 索引\n* `get_mappings` ：获取特定 Elasticsearch 索引的字段映射\n* `search` ：使用提供的查询 DSL 执行 Elasticsearch 搜索\n* `get_shards` ：获取所有或特定索引的分片信息\n\n## 先决条件\n\n* Elasticsearch 实例\n* Elasticsearch 身份验证凭据（API 密钥或用户名/密码）\n* MCP 客户端（例如 Claude Desktop）\n\n## 演示\n\n\n\n## 安装和设置\n\n### 使用已发布的 NPM 包\n\n> \\[!TIP] 使用 Elasticsearch MCP Server 最简单的方法是通过已发布的 npm 包。\n\n1. **配置 MCP 客户端**\n\n * 打开您的 MCP 客户端。查看[MCP 客户端列表](https://modelcontextprotocol.io/clients)，这里我们正在配置 Claude 桌面。\n * 前往\\*\\*“设置”>“开发者”>“MCP 服务器”\\*\\*\n * 单击`Edit Config`并添加具有以下配置的新 MCP 服务器：\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@elastic/mcp-server-elasticsearch\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n2. **开始对话**\n\n * 在 MCP 客户端中打开新对话\n * MCP 服务器应该会自动连接\n * 您现在可以询问有关 Elasticsearch 数据的问题\n\n### 配置选项\n\nElasticsearch MCP 服务器支持配置选项来连接到您的 Elasticsearch：\n\n> \\[!NOTE] 您必须提供 API 密钥或用户名和密码进行身份验证。\n\n| 环境变量 | 描述 | 必需的 |\n| ------------- | ---------------------------------- | --- |\n| `ES_URL` | 您的 Elasticsearch 实例 URL | 是的 |\n| `ES_API_KEY` | 用于身份验证的 Elasticsearch API 密钥 | 不 |\n| `ES_USERNAME` | 用于基本身份验证的 Elasticsearch 用户名 | 不 |\n| `ES_PASSWORD` | Elasticsearch 基本身份验证密码 | 不 |\n| `ES_CA_CERT` | Elasticsearch SSL/TLS 的自定义 CA 证书路径 | 不 |\n\n### 本地开发\n\n> \\[!NOTE] 如果您想修改或扩展 MCP 服务器，请按照这些本地开发步骤操作。\n\n1. **使用正确的 Node.js 版本**\n\n ```bash\n nvm use\n ```\n\n2. **安装依赖项**\n\n ```bash\n npm install\n ```\n\n3. **构建项目**\n\n ```bash\n npm run build\n ```\n\n4. **在 Claude 桌面应用程序中本地运行**\n\n * 打开**Claude 桌面应用程序**\n * 前往\\*\\*“设置”>“开发者”>“MCP 服务器”\\*\\*\n * 单击`Edit Config`并添加具有以下配置的新 MCP 服务器：\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server-local\": {\n \"command\": \"node\",\n \"args\": [\n \"/path/to/your/project/dist/index.js\"\n ],\n \"env\": {\n \"ES_URL\": \"your-elasticsearch-url\",\n \"ES_API_KEY\": \"your-api-key\"\n }\n }\n }\n }\n ```\n\n5. **使用 MCP Inspector 进行调试**\n\n ```bash\n ES_URL=your-elasticsearch-url ES_API_KEY=your-api-key npm run inspector\n ```\n\n 这将启动 MCP 检查器，允许您调试和分析请求。您应该看到：\n\n ```bash\n Starting MCP inspector...\n Proxy server listening on port 3000\n\n 🔍 MCP Inspector is up and running at http://localhost:5173 🚀\n ```\n\n## 贡献\n\n我们欢迎社区的贡献！有关如何贡献的详细信息，请参阅[贡献指南](/docs/CONTRIBUTING.md)。\n\n## 示例问题\n\n> \\[!TIP] 您可以使用 MCP 客户端尝试以下一些自然语言查询。\n\n* “我的 Elasticsearch 集群中有哪些索引？”\n* “显示‘产品’索引的字段映射。”\n* “查找上个月所有超过 500 美元的订单。”\n* “哪些产品获得最多五星评价？”\n\n## 工作原理\n\n1. MCP 客户端分析您的请求并确定需要哪些 Elasticsearch 操作。\n2. MCP 服务器执行这些操作（列出索引、获取映射、执行搜索）。\n3. MCP 客户端处理结果并以用户友好的格式呈现。\n\n## 安全最佳实践\n\n> 避免使用集群管理员权限。请创建具有有限范围的专用 API 密钥，并在索引级别应用细粒度的访问控制，以防止未经授权的数据访问。\n\n您可以创建具有最小权限的专用 Elasticsearch API 密钥来控制对您的数据的访问：\n\n```\nPOST /_security/api_key\n{\n \"name\": \"es-mcp-server-access\",\n \"role_descriptors\": {\n \"mcp_server_role\": {\n \"cluster\": [\n \"monitor\"\n ],\n \"indices\": [\n {\n \"names\": [\n \"index-1\",\n \"index-2\",\n \"index-pattern-*\"\n ],\n \"privileges\": [\n \"read\",\n \"view_index_metadata\"\n ]\n }\n ]\n }\n }\n}\n```\n\n## 执照\n\n该项目采用 Apache License 2.0 许可。\n\n## 故障排除\n\n* 确保您的 MCP 配置正确。\n* 验证您的 Elasticsearch URL 是否可以从您的机器访问。\n* 检查您的身份验证凭据（API 密钥或用户名/密码）是否具有必要的权限。\n* 如果使用带有自定义 CA 的 SSL/TLS，请验证证书路径是否正确以及文件是否可读。\n* 查看终端输出中的错误消息。\n\n如果您遇到问题，请随时在 GitHub 存储库上打开问题。","Chinese","zh-CN","githubUser","locale",{"_83":84,"_13":85,"_94":40,"_95":40,"_16":96,"_97":98,"_31":41,"_110":111,"_118":119,"_120":121,"_171":172,"_177":-5,"_105":152,"_178":179,"_108":180,"_181":182},"addedAt","2025-03-25T19:26:22.191298Z",[86,87,88,89,90,91,92,93],"author:official","category:databases","category:search","hosting:hybrid","language:rust","security_grade:a","quality_grade:a","license_grade:a","descriptionMarkdown","descriptionPlainText",3750,"integrations",[99],{"_100":101,"_29":107,"_108":109},"brand",{"_102":103,"_31":104,"_105":106},"logoSvgPath","M13.394 0C8.683 0 4.609 2.716 2.644 6.667h15.641a4.77 4.77 0 0 0 3.073-1.11c.446-.375.864-.785 1.247-1.243l.001-.002A11.974 11.974 0 0 0 13.394 0zM1.804 8.889a12.009 12.009 0 0 0 0 6.222h14.7a3.111 3.111 0 1 0 0-6.222zm.84 8.444C4.61 21.283 8.684 24 13.395 24c3.701 0 7.011-1.677 9.212-4.312l-.001-.002a9.958 9.958 0 0 0-1.247-1.243 4.77 4.77 0 0 0-3.073-1.11z","Elasticsearch","slug","elasticsearch","Provides access to Elasticsearch indices, allowing users to list indices, inspect field mappings, and execute search queries using full Query DSL capabilities with automatic highlighting.","uid","g2k5ql530d","namespace",{"_112":113,"_105":117},"owner",{"_114":115},"githubAccount",{"_116":117},"login","elastic","redditPostExternalId","1jr2xvx","repository",{"_122":123,"_137":138,"_142":143,"_162":-5,"_163":164,"_165":166,"_170":-5},"argumentsJsonSchema",{"_124":125,"_134":135,"_129":136},"properties",{"_126":127,"_131":132},"ES_URL",{"_29":128,"_129":130},"Your Elasticsearch URL","type","string","ES_API_KEY",{"_29":133,"_129":130},"Your Elasticsearch API key with appropriate permissions","required",[126,131],"object","githubProject",{"_33":139,"_140":141},"# Elasticsearch MCP Server\n\n> [!CAUTION]\n>\n> **WARNING: this MCP server is EXPERIMENTAL.**\n\nConnect to your Elasticsearch data directly from any MCP Client using the Model Context Protocol (MCP).\n\nThis server connects agents to your Elasticsearch data using the Model Context Protocol. It allows you to interact with your Elasticsearch indices through natural language conversations.\n\n## Available Tools\n\n* `list_indices`: List all available Elasticsearch indices\n* `get_mappings`: Get field mappings for a specific Elasticsearch index\n* `search`: Perform an Elasticsearch search with the provided query DSL\n* `esql`: Perform an ES|QL query\n* `get_shards`: Get shard information for all or specific indices\n\n## Prerequisites\n\n* An Elasticsearch instance\n* Elasticsearch authentication credentials (API key or username/password)\n* An MCP Client (e.g. [Claude Desktop](https://claude.ai/download), [Goose](https://block.github.io/goose/))\n\n**Supported Elasticsearch versions**\n\nThis works with Elasticsearch versions `8.x` and `9.x`.\n\n## Installation & Setup\n\n> [!NOTE]\n>\n> Versions 0.3.1 and earlier were installed via `npm`. These versions are deprecated and no longer supported. The following instructions only apply to 0.4.0 and later.\n>\n> To view instructions for versions 0.3.1 and earlier, see the [README for v0.3.1](https://github.com/elastic/mcp-server-elasticsearch/tree/v0.3.1).\n\nThis MCP server is provided as a Docker image at `docker.elastic.co/mcp/elasticsearch`\nthat supports MCP's stdio, SSE and streamable-HTTP protocols.\n\nRunning this container without any argument will output a usage message:\n\n```\ndocker run docker.elastic.co/mcp/elasticsearch\n```\n\n```\nUsage: elasticsearch-mcp-server \n\nCommands:\n stdio Start a stdio server\n http Start a streamable-HTTP server with optional SSE support\n help Print this message or the help of the given subcommand(s)\n\nOptions:\n -h, --help Print help\n -V, --version Print version\n```\n\n### Using the stdio protocol\n\nThe MCP server needs environment variables to be set:\n\n* `ES_URL`: the URL of your Elasticsearch cluster\n* For authentication use either an API key or basic authentication:\n * API key: `ES_API_KEY`\n * Basic auth: `ES_USERNAME` and `ES_PASSWORD`\n* Optionally, `ES_SSL_SKIP_VERIFY` set to `true` skips SSL/TLS certificate verification when connecting\n to Elasticsearch. The ability to provide a custom certificate will be added in a later version.\n\nThe MCP server is started in stdio mode with this command:\n\n```bash\ndocker run -i --rm -e ES_URL -e ES_API_KEY docker.elastic.co/mcp/elasticsearch stdio\n```\n\nThe configuration for Claude Desktop is as follows:\n\n```json\n{\n \"mcpServers\": {\n \"elasticsearch-mcp-server\": {\n \"command\": \"docker\",\n \"args\": [\n \"run\", \"-i\", \"--rm\",\n \"-e\", \"ES_URL\", \"-e\", \"ES_API_KEY\",\n \"docker.elastic.co/mcp/elasticsearch\",\n \"stdio\"\n ],\n \"env\": {\n \"ES_URL\": \"\",\n \"ES_API_KEY\": \"\"\n }\n }\n }\n}\n```\n\n### Using the streamable-HTTP and SSE protocols\n\nNote: streamable-HTTP is recommended, as [SSE is deprecated](https://modelcontextprotocol.io/docs/concepts/transports#server-sent-events-sse-deprecated).\n\nThe MCP server needs environment variables to be set:\n\n* `ES_URL`, the URL of your Elasticsearch cluster\n* For authentication use either an API key or basic authentication:\n * API key: `ES_API_KEY`\n * Basic auth: `ES_USERNAME` and `ES_PASSWORD`\n* Optionally, `ES_SSL_SKIP_VERIFY` set to `true` skips SSL/TLS certificate verification when connecting\n to Elasticsearch. The ability to provide a custom certificate will be added in a later version.\n\nThe MCP server is started in http mode with this command:\n\n```bash\ndocker run --rm -e ES_URL -e ES_API_KEY -p 8080:8080 docker.elastic.co/mcp/elasticsearch http\n```\n\nIf for some reason your execution environment doesn't allow passing parameters to the container, they can be passed\nusing the `CLI_ARGS` environment variable: `docker run --rm -e ES_URL -e ES_API_KEY -e CLI_ARGS=http -p 8080:8080...`\n\nThe streamable-HTTP endpoint is at `http::8080/mcp`. There's also a health check at `http::8080/ping`\n\nConfiguration for Claude Desktop (free edition that only supports the stdio protocol).\n\n1. Install `mcp-proxy` (or an equivalent), that will bridge stdio to streamable-http. The executable\n will be installed in `~/.local/bin`:\n\n ```bash\n uv tool install mcp-proxy\n ```\n\n2. Add this configuration to Claude Desktop:\n\n ```json\n {\n \"mcpServers\": {\n \"elasticsearch-mcp-server\": {\n \"command\": \"//.local/bin/mcp-proxy\",\n \"args\": [\n \"--transport=streamablehttp\",\n \"--header\", \"Authorization\", \"ApiKey \",\n \"http://:/mcp\"\n ]\n }\n }\n }\n ```\n","url","https://github.com/elastic/mcp-server-elasticsearch","githubRepository",{"_144":145,"_146":147,"_148":149,"_150":151,"_31":152,"_112":153,"_155":156,"_157":158,"_160":161},"defaultBranch","main","fullName","elastic/mcp-server-elasticsearch","githubTreeId",175275,"language","Rust","mcp-server-elasticsearch",{"_116":117,"_108":154},"W8FxpqDw6E","recentStargazers",17,"spdxLicense",{"_31":159},"Apache 2.0","stargazers",470,"glamaJson","inspectable",true,"npmPackage",{"_31":167,"_168":169},"@elastic/mcp-server-elasticsearch","weeklyDownloads",1114,"supportedPlatforms","scores",{"_173":174,"_175":174,"_176":174},"license",100,"quality","security","simpleIcon","toolCount",3,"jv4tgnn4d2","updatedAt","2025-09-16T02:45:28.706274Z","meta",[185,188,190,197,200,202,205,208,211,214,217,219,222,225,227,229,231,233,235],{"_186":187},"title","Elasticsearch MCP Server | Glama",{"_189":40,"_31":29},"content",{"_191":192,"_193":194,"_195":196},"href","https://glama.ai/mcp/servers/@elastic/mcp-server-elasticsearch","rel","canonical","tagName","link",{"_189":41,"_198":199},"property","og:title",{"_189":40,"_198":201},"og:description",{"_189":203,"_198":204},"https://glama.ai/logo.png","og:logo",{"_189":206,"_198":207},"https://glama.ai/mcp/servers/@elastic/mcp-server-elasticsearch/og-image","og:image",{"_189":209,"_198":210},"630","og:image:height",{"_189":212,"_198":213},"1200","og:image:width",{"_189":215,"_198":216},"website","og:type",{"_189":192,"_198":218},"og:url",{"_189":220,"_198":221},"Glama – MCP Hosting Platform","og:site_name",{"_189":223,"_31":224},"summary_large_image","twitter:card",{"_189":220,"_31":226},"twitter:title",{"_189":40,"_31":228},"twitter:description",{"_189":206,"_31":230},"twitter:image",{"_189":209,"_31":232},"twitter:image:height",{"_189":212,"_31":234},"twitter:image:width",{"_236":237},"script:ld+json",{"_238":239,"_240":241},"@context","http://schema.org","@graph",[242],{"_238":243,"_244":245,"_246":247},"https://schema.org","@type","BreadcrumbList","itemListElement",[248,255,259,262],{"_244":249,"_250":251,"_31":252,"_253":254},"ListItem","item","/","Glama","position",1,{"_244":249,"_250":256,"_31":257,"_253":258},"/mcp","MCP",2,{"_244":249,"_250":260,"_31":261,"_253":179},"/mcp/servers","Servers",{"_244":249,"_250":263,"_31":41,"_253":264},"/mcp/servers/@elastic/mcp-server-elasticsearch",4,"visitorIsMaintainer",false,"routes/_public/mcp/servers/~namespace/~slug/_pages/reviews/_route",{"_80":-5,"_27":269,"_183":289,"_325":-5},{"_83":84,"_13":270,"_94":40,"_95":40,"_16":96,"_97":271,"_31":41,"_110":274,"_118":119,"_120":277,"_171":288,"_177":-5,"_105":152,"_178":179,"_108":180,"_181":182},[86,87,88,89,90,91,92,93],[272],{"_100":273,"_29":107,"_108":109},{"_102":103,"_31":104,"_105":106},{"_112":275,"_105":117},{"_114":276},{"_116":117},{"_122":278,"_137":283,"_142":284,"_162":-5,"_163":164,"_165":287,"_170":-5},{"_124":279,"_134":282,"_129":136},{"_126":280,"_131":281},{"_29":128,"_129":130},{"_29":133,"_129":130},[126,131],{"_33":139,"_140":141},{"_144":145,"_146":147,"_148":149,"_150":151,"_31":152,"_112":285,"_155":156,"_157":286,"_160":161},{"_116":117,"_108":154},{"_31":159},{"_31":167,"_168":169},{"_173":174,"_175":174,"_176":174},[290,292,294,296,298,299,300,301,302,303,304,305,306,307,308,309,310,311,312],{"_186":291},"Reviews | Elasticsearch MCP Server | Glama",{"_189":293,"_31":29},"Read community reviews and feedback for Elasticsearch MCP Server. Discover user experiences, ratings, strengths, and potential limitations of this MCP implementation from actual users.",{"_191":295,"_193":194,"_195":196},"https://glama.ai/mcp/servers/@elastic/mcp-server-elasticsearch/reviews",{"_189":297,"_198":199},"Reviews | Elasticsearch MCP Server",{"_189":293,"_198":201},{"_189":203,"_198":204},{"_189":206,"_198":207},{"_189":209,"_198":210},{"_189":212,"_198":213},{"_189":215,"_198":216},{"_189":295,"_198":218},{"_189":220,"_198":221},{"_189":223,"_31":224},{"_189":220,"_31":226},{"_189":293,"_31":228},{"_189":206,"_31":230},{"_189":209,"_31":232},{"_189":212,"_31":234},{"_236":313},{"_238":239,"_240":314},[315],{"_238":243,"_244":245,"_246":316},[317,318,319,320,321],{"_244":249,"_250":251,"_31":252,"_253":254},{"_244":249,"_250":256,"_31":257,"_253":258},{"_244":249,"_250":260,"_31":261,"_253":179},{"_244":249,"_250":263,"_31":41,"_253":264},{"_244":249,"_250":322,"_31":323,"_253":324},"/mcp/servers/@elastic/mcp-server-elasticsearch/reviews","Reviews",5,"review","actionData","errors"]

MCP directory API