Elasticsearch MCP integration
Queries an index with filters and time ranges, reads its mapping first, and confirms the cluster is reachable before it runs.
4actions available
What your agent can do with Elasticsearch
Every action runs live through MCP. Nothing to build, nothing to maintain.
Query index
Lyro runs filtered searches across your Elasticsearch index with time-range and pagination support. Returns only the data that matches your criteria.
List indices
Lyro shows all your Elasticsearch indices and their status. Helps you pick which dataset to query for your analysis.
How businesses use Elasticsearch + Lyro
Each card is one request a support team gets, and the Elasticsearch actions Lyro runs to close it.
Answer a question from documents in an index
Lyro finds the index that holds the data, then queries it with filters, a time range and pagination, so a question about recent records is answered from the cluster itself.
List IndicesQuery IndexCheck the cluster and the mapping before querying
Lyro pings the cluster to confirm it is running and reads the index mapping to see which fields and field types exist, so a query is not built against a field that was never indexed.
Ping ClusterGet Index Schema
How it works
Get started in 3 steps
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Elasticsearch actions it has and picks the ones a request needs.
- 01
Connect Elasticsearch
Authorize the Elasticsearch account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
- 02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Elasticsearch actions that close it and chains as many as the request needs.
- 03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free
Everything else about Elasticsearch
Setup, permissions, and the limits of what Lyro can do inside Elasticsearch.
No. The four actions are Query Index, Get Index Schema, List Indices and Ping Cluster, all reads. Lyro searches and reports on what is already in the cluster; writing documents and managing indices stays with whatever pipeline owns them today.
Every action available in Elasticsearch
All 4 actions your agent can call on Elasticsearch, straight from the live MCP connection.
Get index schema
Get the complete schema/mapping of a specific Elasticsearch index.
List indices
List all available Elasticsearch indices.
Ping cluster
Ping the Elasticsearch cluster and check if it is running.
Query index
Query an Elasticsearch index with various filters, time ranges, and pagination support.
The tools Elasticsearch sits next to
Same connection, same setup. Pick the next one your team already uses.
21risk
Answers compliance status by site or category, lists audit reports, and retrieves open items with their cost and monthly trend.
Companyenrich
Enriches companies from a domain, resolves an email to the person behind it, finds lookalike accounts with a free count first, and runs bulk exports.
Gigasheet
Puts a plain-language question to a huge dataset, cleans duplicate and broken rows, derives formula and label columns, and exports the finished view on request.
Microsoft clarity
Runs the Microsoft Clarity data export so site behaviour figures arrive inside the conversation.
Platerecognizer
Decodes a plate from an uploaded photo with a confidence score and region, and reports the month's Snapshot recognition usage.
Solcast
Lists and opens PV power resources, creates or patches their technical settings, and pulls historical irradiance and weather for a coordinate.
Ready to connect Elasticsearch?
Authorize the account and your agent has all 4 actions from the first conversation.