Elasticsearch
for LuumenAI
Search your Elasticsearch indices for context, without leaving the terminal
Ask about your logs and documents where you already work. Luumen checks the cluster is up with ELASTICSEARCH_PING_CLUSTER, finds the right index with ELASTICSEARCH_LIST_INDICES, reads its mapping via ELASTICSEARCH_GET_INDEX_SCHEMA, then runs filtered, time-bounded searches with ELASTICSEARCH_QUERY_INDEX. Read-only, over basic auth.
The Elasticsearch toolbox
4 tools, all read-only. They answer instantly, and every call is logged.
- ReadGet Index SchemaGet the complete schema/mapping of a specific Elasticsearch index.
- ReadList IndicesList all available Elasticsearch indices.
- ReadPing ClusterPing the Elasticsearch cluster and check if it is running.
- ReadQuery IndexQuery an Elasticsearch index with various filters, time ranges, and pagination support.
Questions
Authorize once with Basic auth. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
No. Every one of the 4 tools LuumenAI has for Elasticsearch is read-only, so it can answer questions from Elasticsearch but cannot change anything in it. Reads are not gated — they answer immediately, and each one is recorded on the audit trail with the actor and the result.
You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.
Every call to Elasticsearch is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
PostgreSQLQuery PostgreSQL state safely; maintenance held for approval.
MySQLQuery MySQL state safely; maintenance held for approval.
Microsoft SQL ServerQuery Microsoft SQL Server state safely; maintenance held for approval.Oracle DatabaseQuery Oracle Database state safely; maintenance held for approval.Put Elasticsearch to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.