Ext Ops Panel
Open dashboard
Comparison

Elasticsearch vs Jarroba Tools · Logs

Elasticsearch is an MCP server published by elastic. Marketplaces we read that list it: 1 (Docker MCP Catalog). Jarroba Tools · Logs is an MCP server published by Invarato. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceElasticsearchJarroba Tools · Logs
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
Official MCP Registry Not listed Listed
Version: 0.1.11
Downloads/month (npm): 1 485
Downloads/week (npm): 283
Forks (GitHub): 0
Stars (GitHub): 0
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 Jarroba Tools · Logs
FactElasticsearchJarroba Tools · Logs
Marketplaces that list it11
Stars (GitHub) (differs)725 (better)0 (worse)
Pulls (Docker Hub) (differs)46 549No figure on Docker Hub
Forks (GitHub) (differs)161 (better)0 (worse)
Last release (differs)Not published2026-10-21
Where it runs (differs)On your machine (mcp/elasticsearch)On your machine (@jarroba/mcp-logs)
Transportstdiostdio
Tools it declares (differs)5Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 0
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/elastic/mcp-server-elasticsearchgithub.com/invarato/jarroba-mcp
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Elasticsearch

In its own words, on Docker MCP Catalog:

Interact with your Elasticsearch indices through natural language conversations.

Jarroba Tools · Logs

In its own words, on Official MCP Registry:

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

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)

Jarroba Tools · Logs As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio jarroba-tools-logs -- npx -y @jarroba/mcp-logs

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

Tools each declares

The marketplaces of Jarroba Tools · Logs publish no list of tools, so we do not compare tools.

Settings each asks for

Only Elasticsearch asks for

  • ES_API_KEY (secret)
  • ES_URL

Only Jarroba Tools · Logs asks for

  • JARROBA_MCP_DOMAINS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Elasticsearch · What it can do: Jarroba Tools · Logs · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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