What do I need to run Elasticsearch MCP Server?
You need a running Elasticsearch instance, authentication credentials (an API key or a username/password pair), and an MCP Client such as Claude Desktop or Cursor.
@awesimon
基本情報
Elasticsearch MCP server with available features including mappings management, search and indexing, and index management etc.
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"elasticsearch-mcp": {
"command": "npx",
"args": [
"-y",
"@awesome-ai/elasticsearch-mcp"
],
"env": {
"ES_HOST": "your-elasticsearch-host",
"ES_API_KEY": "your-api-key"
}
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。
A Model Context Protocol server that connects MCP Clients—such as Claude Desktop or Cursor—to an Elasticsearch cluster, enabling users to interact with their indices and data through natural language conversations.
Configure your MCP Client using npx with the published npm package (@awesome-ai/elasticsearch-mcp), providing your Elasticsearch host and authentication credentials via environment variables (ES_HOST, ES_API_KEY or ES_USERNAME/ES_PASSWORD). After setup, the server connects automatically, and you can query your cluster using everyday language.
You need a running Elasticsearch instance, authentication credentials (an API key or a username/password pair), and an MCP Client such as Claude Desktop or Cursor.
You must provide either an `ES_API_KEY` or both `ES_USERNAME` and `ES_PASSWORD` via environment variables. The configuration accepts legacy variable names as fallbacks.
Yes. Set the `ES_HOST` environment variable to a comma-separated list of node URLs. The client automatically handles failover and load balancing across the configured nodes.
Clone the repository, install dependencies (`npm install`), build the project (`npm run build`), then point your MCP Client configuration to the built `dist/index.js` file using the `node` command.
Yes, use the MCP Inspector. Run `ES_HOST=your-url ES_API_KEY=your-key npm run inspector`, then access the inspector UI at `http://127.0.0.1:6274` to inspect requests and responses.
A Model Context Protocol (MCP) server implementation that provides database capabilities for Chroma

Model Context Protocol Servers
Drop-in Apache Spark replacement written in Rust, unifying batch processing, stream processing, and compute-intensive AI workloads.

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.
コメント