Mcp Elasticsearch
Let your coding agent query Elasticsearch or OpenSearch read-only for logs, search hits, index mappings, and cluster health without writing custom API glue.
Overview
mcp-elasticsearch is an Operate-phase MCP server that gives AI agents read-only Elasticsearch/OpenSearch search, index, mapping, count, and health tools.
What is this MCP server?
- Read-only search against Elasticsearch/OpenSearch indices
- List indices and inspect field mappings for schema debugging
- Count documents and run aggregations-style queries via agent tools
- Cluster health visibility for quick ops triage
- Stdio MCP server via npm @infoinlet/mcp-elasticsearch v0.1.1
- Server version 0.1.1
- npm package @infoinlet/mcp-elasticsearch
- stdio transport
What problem does it solve?
Debugging search and log indices means context-switching to Kibana, Dev Tools, or raw REST calls while your agent cannot see cluster state.
Who is it for?
Builders who self-host Elasticsearch or OpenSearch and want safe, agent-driven inspection during incidents or feature work.
Skip if: Teams that need write, bulk ingest, or index administration from the agent—this server is read-only by design.
What do I get? / Deliverables
Your agent can inspect indices and run read-only searches from the IDE so you fix mapping and query issues faster.
- Agent-callable read-only search and index inspection against your cluster
- Mapping and count answers inlined in chat during debug sessions
- Health status checks without opening a separate ops console
Recommended MCP Servers
Journey fit
Operate is where solo builders inspect live search clusters, debug indexing issues, and validate what is actually stored after ship. Monitoring covers health checks, document counts, and search against production-like indices without mutating data.
How it compares
Read-only database MCP integration, not a managed OpenSearch UI or a one-off curl skill.
Common Questions / FAQ
Who is mcp-elasticsearch for?
Solo builders and small teams using Elasticsearch or OpenSearch who want Claude Code or Cursor to query and inspect clusters without write access.
When should I use mcp-elasticsearch?
Use it during operate and monitoring work when you need searches, mappings, counts, or health checks while debugging search or log pipelines.
How do I add mcp-elasticsearch to my agent?
Install @infoinlet/mcp-elasticsearch from npm, add a stdio MCP entry in your client config, and point it at your cluster URL and read credentials.