Elasticsearch MCP Server

✓ verified

Search and explore Elasticsearch indices from chat.

Don't have ToolPiper? We'll take you to the download.

Open repository →

Publisher

Elastic

License

Apache-2.0

Transport

Local subprocess

Tools

4

What this server does

Elastic's official MCP server lets the assistant explore your Elasticsearch data conversationally. List indices, read field mappings, run query DSL or ES|QL searches, and pull back matching documents. It is the natural companion to a logging or search workload: ask 'how many 500s did the API serve yesterday?' and let the model build the query against the right index. Scope the API key to read-only on just the indices you want the assistant to see.

Tools included

  • list_indices

    List available indices.

  • get_mappings

    Get the field mappings for an index.

  • search

    Run a query DSL or simple search against an index.

  • esql

    Run an ES|QL query.

The authoritative list comes from the server's tools/list at runtime. This catalog entry may lag the upstream until the next ToolPiper release.

Install in ToolPiper

ToolPiper handles the JSON configuration. Click Install, fill in any required tokens, and the server is ready in your chat.

Don't have ToolPiper? We'll take you to the download.

Install in another client

Install in another MCP client (Claude Desktop, Cursor, Continue, Cline)

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json.

{
  "mcpServers": {
    "elasticsearch": {
      "command": "npx",
      "args": [
        "-y",
        "@elastic/mcp-server-elasticsearch"
      ]
    }
  }
}

Example prompts

  • "List my indices and tell me which one holds application logs."

  • "Search the logs index for errors from the payments service in the last hour."

  • "Run an ES|QL query to count requests grouped by status code."

Security notes

The API key is the access boundary. Mint a key scoped to read-only on only the indices you want exposed, since logs and search indices often contain PII, request bodies, and tokens. Treat the key as a credential and rotate it if it leaks. The URL and key together grant whatever the key allows, so least privilege matters here.

Related tools