Ext Ops Panel
Open dashboard
Comparison

Elasticsearch vs log-sleuth

log-sleuth is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

Elasticsearch is an MCP server published by elastic. Marketplaces we read that list it: 1 (Docker MCP Catalog). log-sleuth is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceElasticsearchlog-sleuth
Docker MCP Catalog Listed
Version: sha256:9c978b8277e3
Forks (GitHub): 161
Pulls (Docker Hub): 46 549
Stars (Docker Hub): 17
Stars (GitHub): 725
Not marked · First seen
Not listed
Community marketplace barnburner121/claude-plugin-marketplace Not listed Removed on 2026-10-18
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Elasticsearch vs log-sleuth
FactElasticsearchlog-sleuthno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)7253
Pulls (Docker Hub) (differs)46 549No figure on Docker Hub
Forks (GitHub) (differs)1610
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/elasticsearch)On your machine (@barnburner121/plugin-hub-mcp)
Transport (differs)stdioNot stated
Tools it declares (differs)5Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/elastic/mcp-server-elasticsearchgithub.com/barnburner121/claude-plugin-marketplace
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of log-sleuth

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • gonzo

    Set up and use Gonzo, the open-source terminal log analysis tool. Detects deployment platforms (Vercel, Supabase, K8s, Docker, AWS, Cloudflare, Fly, Render, Railway, Netlify…

    by ControlTheory · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • ctrlb-decompose

    Analyze log files with ctrlb-decompose — pattern clustering, anomaly detection, and severity scoring

    by CtrlB · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • LogsLoom

    Ingest and search LogsLoom logs from coding agents.

    by efim23 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Log Detective MCP

    MCP server providing log snippet and Python traceback extraction tools.

    by fedora-copr · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Jarroba Tools · Logs

    Lets your AI read a CI log far too big for its context. 12 tools, takes a file path.

    by Invarato · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • log-analyzer-mcp io.github.Fato07/log-analyzer-mcp

    AI-powered log analysis - parse, search, extract errors across 9+ formats

    by Fato07 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

Elasticsearch

In its own words, on Docker MCP Catalog:

Interact with your Elasticsearch indices through natural language conversations.

log-sleuth

In its own words, on Community GitHub marketplaces:

Analyze log files for patterns, search with structured queries, get logging recommendations, and correlate across services

How to run each

Elasticsearch As a local MCP server: Docker image

Claude Code
claude mcp add --env "ES_API_KEY=<YOUR_ES_API_KEY>" --transport stdio elasticsearch -- docker run -i --rm -e ES_API_KEY mcp/elasticsearch

Requires: ES_API_KEY (secret)

log-sleuth

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of log-sleuth publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of log-sleuth publish no settings it asks for, so we do not compare settings.

What it can do: Elasticsearch · What it can do: log-sleuth · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built