MCP serverby elasticHEU
Better agent tooling for Elasticsearch
Integration gap · Measured demandOverall 49.5 / 100 DERConfidence Medium DERCalculated
326 public GitHub issues mention "Elasticsearch mcp" (checked 2026-11-21) SRC, while 27 indexed products mention Elasticsearch DER. On the six weighted components it scores 49.5 of 100, confidence Medium, as of 2026-11-21.
Score breakdown
Contribution = weight × component score. The contributions add up to the overall score.
| Component | Weight | Score | Score (0–100) | Contribution | Kind |
|---|---|---|---|---|---|
| Demand | 0.25 | 32.0 | 0.25 × 32.0 = 8.00 | Measured | |
| Competition gap | 0.20 | 60.0 | 0.20 × 60.0 = 12.00 | Measured | |
| Monetisation | 0.20 | 35.0 | 0.20 × 35.0 = 7.00 | Heuristic | |
| Growth (relative) | 0.15 | 44.0 | 0.15 × 44.0 = 6.60 | Measured | |
| Feasibility | 0.10 | 80.0 | 0.10 × 80.0 = 8.00 | Heuristic | |
| Distribution | 0.10 | 79.0 | 0.10 × 79.0 = 7.90 | Measured | |
| Overall | 1.00 | 49.50 → 49.5 |
Solid bars are measured components; dashed outlines are rules of thumb. The full formula is on the radar page.
Confidence: Medium
Rule: Medium when at least 50 GitHub issues mention the integration and at least 10 indexed products mention it; otherwise Low. Nothing is rated High.
What would raise it
- Medium is the highest level the rules assign. High would need a second, independent demand source (search volume or marketplace installs), which is not connected.
The opportunity
All text in this section is generated by rule from the record. It is a starting point, not research.
- Description
- Developers are asking for Elasticsearch access from AI agents more than the current supply of well-maintained tools would suggest.DER
- Problem
- Agents need to read from and act on Elasticsearch. Only some of the existing tools are both documented and actively maintained.DER
- Target users
- Developers and individuals who use ElasticsearchHEU
- Product form
- MCP server (optionally bundled as a plugin with skills)HEU
- Revenue model
- Open source with paid hosting or supportHEU
- Complexity
- Low to mediumHEU
- Competition level
- HighDER
- Subject
- Elasticsearch (integration)
Evidence for
3 row(s) from opportunity_evidence.
Competition gapMeasuredDERvalue 15
27 indexed products mention Elasticsearch; 15 of them have a complete record and a repository pushed in the last 180 days.
FeasibilityHeuristicHEU
Elasticsearch has a public API (documentation linked).
DistributionMeasuredDERvalue 37
37 of 47 tracked agent platforms document MCP support, so one MCP server can reach all of them.
Evidence against
3 row(s) from opportunity_evidence.
DemandMeasuredDERvalue 326
326 public GitHub issues contain the phrase "Elasticsearch mcp" (checked 2026-11-21); that is the 32th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.
MonetisationHeuristicHEU
Elasticsearch is not primarily a paid business product. This is a rule of thumb, not revenue data.
Growth (relative)MeasuredDERvalue 13
13 products launched in the last 90 days versus 4 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.
Existing products
All Elasticsearch productsThe most notable profiled products mentioning Elasticsearch (up to 8). 27 indexed in total.
Agent skillby Shy2593666979HEU
Infrastructureby didililiHEU
MCP serverby cr7258SRC
MCP serverby thomasxmSRC
MCP serverby TocharianOUSRC
Agent skillby kubesphereSRC
MCP serverby TocharianOUSRC
Where it could be distributed
All platforms37 of 47 tracked agent platforms document MCP support CUR, so one MCP server could reach all of them. No pairing has been tested.
ContinueOpenCodeClaude CodeCodexGemini CLIZedOpenHandsClineWarpgooseQwen CodeRoo Code+25 more
Channels: Official MCP Registry listing, plugin marketplaces for Claude/Cursor/Codex, and the integration vendor's own app directory where one exists. HEU
Data coverage
- Indexed products
- 27DER
- With a full profile
- 8+DER
- Launches, last 90 days
- 13 vs 4 in the 90 beforeSRC
- Demand measured
- SRC
- Segment calculated
- Score calculated
Risks and counterarguments
- The vendor may ship (or already ships) an official Elasticsearch server, which usually becomes the default.
- Issue mentions measure developer discussion, not willingness to pay.
- 326 public GitHub issues contain the phrase "Elasticsearch mcp" (checked 2026-11-21); that is the 32th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.
- Elasticsearch is not primarily a paid business product. This is a rule of thumb, not revenue data.
- 13 products launched in the last 90 days versus 4 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.
Assumptions
What has to be true for the score to mean anything.
- Mentions of "Elasticsearch mcp" in GitHub issues reflect developers wanting Elasticsearch access from agents.
- Products that mention the integration in their description or package metadata are the competing supply; ones that do not name it are missed.
- "Well-maintained" means data completeness ≥ 0.6 and a repository push in the last 180 days.
- Percentiles compare this integration only with the other integrations tracked, not with the wider market.
- A platform that documents MCP support can run any MCP server; no pairing has been tested.
How to verify this yourself
- Run the demand query on GitHub: https://github.com/search?q=%22Elasticsearch%20mcp%22%20in%3Atitle%2Cbody%20is%3Aissue&type=issues. Compare the count with 326 on 2026-11-21; read a sample of issues to see whether they ask for agent access or merely mention it.
- Check the supply on the Elasticsearch page and search the official MCP Registry and the vendor's own app directory for an official server.
- Download the record with all evidence: /api/dataset/opportunities.json.
Page data last updated .