Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Computer or cloud
Indexsearch
What it does
Elasticsearch tools: indices, mappings, query DSL search, ES|QL, and shards.
- Connects Runs on your computer
- Account or key No key needed
- Category Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Install Node.js
One time only; it works for every server that needs Node.js
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "indexsearch": { "command": "npx", "args": [ "-y", "@reneturcios/indexsearch", "mcp" ] } } }Quit Claude and open it again
Try it
Use Indexsearch and tell me what you can do for me, then show me one thing✓ If Claude says it is using Indexsearch or shows a Indexsearch tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Indexsearch yet
Indexsearch runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect Indexsearch
- Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- Install Node.js on your computer first (one time)
- Install Node.js on your computer first (one time)
- Install Node.js on your computer first (one time)
B · Others in Search & AI memory that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Context7✓ ChatGPT
- AIHOT✓ ChatGPT
- Sui Knowledge Base (kapa.ai)✓ ChatGPT
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Install Node.js
One time only; it works for every server that needs Node.js
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user indexsearch -- npx -y @reneturcios/indexsearch mcpType /mcp in Claude Code
You should see Indexsearch listed as connected
Try it
Use Indexsearch and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Indexsearch or shows a Indexsearch tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Install Node.js
One time only; it works for every server that needs Node.js
Open the AI chat in Cursor in Agent mode
Try it
Use Indexsearch and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Indexsearch or shows a Indexsearch tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Install Node.js
One time only; it works for every server that needs Node.js
Open the AI chat in VS Code in Agent mode
Try it
Use Indexsearch and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Indexsearch or shows a Indexsearch tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user indexsearch -- npx -y @reneturcios/indexsearch mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"indexsearch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/indexsearch",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"indexsearch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/indexsearch",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"indexsearch": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/indexsearch",
"mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
- Downloads per weeki
- 286/wk
- Connection
- Runs on your computer
- Latest versioni
- 0.1.0
- Categoryi
- Search & AI memory
- Published to registryi
- Oct 31, 2026
- Code last changedi
- Oct 31, 2026
- Maker
- CloudCorpRecords
- Packages
npm: @reneturcios/indexsearchoci: ghcr.io/cloudcorprecords/indexsearch:0.1.0- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 13, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
- ✓ Pass
Still maintained
Code last changed 13 days ago
- ✓ Pass
Has a licence
Uses MIT
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Search & AI memoryi
- More stars than 0% of the other 6058 servers in this category
- Published to the registry more recently than 74% of the other 6058 servers in this category
- Basic checks equal to or better than 100% of the other 6058 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Indexsearch safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 13 days ago, and the latest version (0.1.0) reached the registry 13 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
What can I use instead?
In the same category: Context7, Codebase Memory, Ruflo
Others in the same category
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Runs on your computer
Ruflo
Agent teams, swarms, memory and hooks for Claude Code and Codex, served over MCP.
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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-indicesOr run the container image:
docker run -i ghcr.io/cloudcorprecords/indexsearchThe 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 | unset (no auth) |
CLI
# List indicesindexsearch 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 mcpMCP 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 | QL query |
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 installnpm 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.