Ext Ops Panel
Open dashboard
Comparison

Elasticsearch vs io.github.VictoriaMetrics-Community/mcp-victoriametrics

Elasticsearch is an MCP server published by elastic. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.VictoriaMetrics-Community/mcp-victoriametrics is an MCP server published by VictoriaMetrics-Community. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-30. 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
MarketplaceElasticsearchio.github.VictoriaMetrics-Community/mcp-victoriametrics
Docker MCP Catalog Listed
Version: sha256:9c978b8277e3
Forks (GitHub): 161
Pulls (Docker Hub): 47 440
Stars (Docker Hub): 17
Stars (GitHub): 727
Not marked · First seen
Listed
Version: sha256:177f32eb9164
Forks (GitHub): 35
Stars (GitHub): 241
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 1.18.0
Forks (GitHub): 35
Stars (GitHub): 241
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 io.github.VictoriaMetrics-Community/mcp-victoriametrics
FactElasticsearchio.github.VictoriaMetrics-Community/mcp-victoriametrics
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)727 (better)241 (worse)
Pulls (Docker Hub) (differs)47 440No figure on Docker Hub
Forks (GitHub) (differs)161 (better)35 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/elasticsearch)On your machine (ghcr.io/victoriametrics-community/mcp-victoriametrics:1.18.0)
Transportstdiostdio
Tools it declares (differs)520
Environment variables it asks for (differs)2, secrets among them: 19, secrets among them: 1
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/elastic/mcp-server-elasticsearchgithub.com/victoriametrics-community/mcp-victoriametrics
Changes in the last 7 days00
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.

io.github.VictoriaMetrics-Community/mcp-victoriametrics

In its own words, on Official MCP Registry:

MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation

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)

io.github.VictoriaMetrics-Community/mcp-victoriametrics As a local MCP server: Docker image

Claude Code
claude mcp add --env "VMC_API_KEY=<YOUR_VMC_API_KEY>" --env "VM_INSTANCE_BEARER_TOKEN=<YOUR_VM_INSTANCE_BEARER_TOKEN>" --env "VM_INSTANCE_ENTRYPOINT=<YOUR_VM_INSTANCE_ENTRYPOINT>" --env "VM_INSTANCE_TYPE=<YOUR_VM_INSTANCE_TYPE>" --transport stdio mcp-victoriametrics -- docker run -i --rm -e VMC_API_KEY -e VM_INSTANCE_BEARER_TOKEN -e VM_INSTANCE_ENTRYPOINT -e VM_INSTANCE_TYPE ghcr.io/victoriametrics-community/mcp-victoriametrics:1.18.0

Requires: VMC_API_KEY (secret), VM_INSTANCE_BEARER_TOKEN (secret), VM_INSTANCE_ENTRYPOINT, VM_INSTANCE_TYPE

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

Tools each declares

Only Elasticsearch declares

  • esql
  • get_mappings
  • get_shards
  • list_indices
  • search

Only io.github.VictoriaMetrics-Community/mcp-victoriametrics declares

  • active_queries
  • alerts
  • documentation
  • downsampling_filters_debug
  • explain_query
  • flags
  • label_values
  • labels
  • metric_relabel_debug
  • metrics
  • metrics_metadata
  • prettify_query
Show the remaining 8
  • query
  • query_range
  • retention_filters_debug
  • rules
  • series
  • tenants
  • top_queries
  • tsdb_status

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Elasticsearch asks for

  • ES_API_KEY (secret)
  • ES_URL

Only io.github.VictoriaMetrics-Community/mcp-victoriametrics asks for

  • MCP_DISABLED_TOOLS
  • MCP_DISABLE_RESOURCES
  • MCP_HEARTBEAT_INTERVAL
  • MCP_LISTEN_ADDR
  • MCP_SERVER_MODE
  • VMC_API_KEY (secret)
  • VM_INSTANCE_BEARER_TOKEN (secret)
  • VM_INSTANCE_ENTRYPOINT
  • VM_INSTANCE_HEADERS
  • VM_INSTANCE_TYPE

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

What it can do: Elasticsearch · What it can do: io.github.VictoriaMetrics-Community/mcp-victoriametrics · 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