Server data from the Official MCP Registry
Elasticsearch tools: indices, mappings, query DSL search, ES|QL, and shards.
About
Elasticsearch tools: indices, mappings, query DSL search, ES|QL, and shards.
Security Report
indexsearch is a straightforward Elasticsearch client exposing five read-oriented tools over the cluster's HTTP API, with no shell execution, file access, or obfuscated code found. The main concerns are that authentication is optional and off by default, and that an ES_API_KEY configured against a plain http:// URL would be sent in cleartext. Permissions (network HTTP to the configured cluster and environment variable reads) match the stated purpose. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
8 files analyzed · 9 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
What You'll Need
Set these up before or after installing:
Environment variable: ES_URL
Environment variable: INDEXSEARCH_URL
Environment variable: ES_API_KEY
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"indexsearch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/indexsearch@0.1.0"
],
"env": {
"ES_URL": "your-es-url-here",
"ES_API_KEY": "your-es-api-key-here",
"INDEXSEARCH_URL": "your-indexsearch-url-here"
}
}
}
}Some servers take additional arguments. See the repository for details.
Documentation
View on GitHubFrom the project's GitHub README.
indexsearch
indexsearch gives an agent — or you, at a terminal — the five core Elasticsearch tools: see which indices exist, read an index's field mappings, run a search in query DSL, run an ES|QL query, and inspect shard placement. Everything goes through the cluster's own HTTP API; there is no bundled client library and no second query language to learn.
Each tool call is first mapped to a plain HTTP request — method, path,
and JSON body — and that mapping is the whole contract:
GET /_cat/indices?format=json, GET /{index}/_mapping,
POST /{index}/_search, POST /_query, GET /_cat/shards. Transport
is an injectable fetch function, which is what the test suite drives;
no live cluster is needed to verify behaviour, and no result is ever
invented when a cluster is unreachable or answers with an error.
Install
npx @reneturcios/indexsearch list-indices
Or run the container image:
docker run -i ghcr.io/cloudcorprecords/indexsearch
The container defaults to the MCP server (see below). Pass CLI
arguments to use it as a CLI instead, and pass the cluster settings as
environment variables (-e ES_URL=...).
Configuration
| Variable | Meaning | Default |
|---|---|---|
ES_URL | Cluster base URL | http://localhost:9200 |
INDEXSEARCH_URL | Fallback cluster base URL when ES_URL is unset | — |
ES_API_KEY | API key, sent as Authorization: ApiKey <key> | unset (no auth) |
CLI
# List indices
indexsearch list-indices
# Read one index's field mappings
indexsearch mappings products
# Search with query DSL (a bare clause, or a full {"query": ...} body)
indexsearch search products '{"match":{"name":"shoes"}}'
# Run an ES|QL query
indexsearch esql 'FROM products | SORT price DESC | LIMIT 5'
# Shard information for every index, or for one
indexsearch shards
indexsearch shards products
# Start the MCP server
indexsearch mcp
indexsearch --version
Exit codes: 0 on success, 1 when the request or the cluster
fails (the error names the HTTP status or the unreachable URL),
2 for usage errors.
Index names are validated before any request is made: names carrying
characters Elasticsearch forbids in index names (whitespace, /, *,
?, ", <, >, |, ,, #, :, \) are rejected locally.
MCP server
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
npx -y @reneturcios/indexsearch mcp
MCP client configuration:
{
"mcpServers": {
"indexsearch": {
"command": "npx",
"args": ["-y", "@reneturcios/indexsearch", "mcp"],
"env": { "ES_URL": "http://localhost:9200" }
}
}
}
Tools
| Tool | Required | Optional | HTTP request | What it does |
|---|---|---|---|---|
list_indices | — | — | GET /_cat/indices?format=json | List all available indices |
get_mappings | index | — | GET /{index}/_mapping | Get field mappings for an index |
search | index, query (object) | — | POST /{index}/_search with { "query": ... } | Search using query DSL |
esql | query (string) | — | POST /_query with { "query": ... } | Run an ES |
get_shards | — | index | GET /_cat/shards[/{index}]?format=json | Get shard information for all or specific indices |
Replies are returned as the cluster's parsed JSON. A non-JSON reply is
returned under a raw key rather than being dropped, and an empty
reply reads as an empty object.
Development
npm install
npm run build # tsc -> dist/
npm test # node test runner over test/*.test.ts, no network, no live cluster
npm run dev # run the CLI from source via tsx
Request construction, validation, header and body assembly, error surfacing, and settings resolution are all covered by tests that drive the core through a fake fetch and assert the exact paths and bodies.
License
MIT — see LICENSE.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
