Ext Ops Panel
Open dashboard
Comparison

elastic-sense vs Elasticsearch

elastic-sense is a plugin bundle for AI coding tools published by ahmidbbc. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Elasticsearch is an MCP server published by TocharianOU. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplaceelastic-senseElasticsearch
Claude Code: claude-plugins-community Listed
Version: 1.2.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.9.1
Downloads/month (npm): 550
Downloads/week (npm): 265
Forks (GitHub): 6
Stars (GitHub): 8
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

elastic-sense vs Elasticsearch
Factelastic-senseElasticsearch
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)8 (better)
Forks (GitHub) (differs)0 (worse)6 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@tocharianou/elasticsearch-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)5, secrets among them: 110, secrets among them: 2
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/ahmidbbc/elastic-sensegithub.com/tocharianou/elasticsearch-mcp
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

elastic-sense

In its own words, on Claude Code: claude-plugins-community:

ElasticSense is a Claude Code plugin for Elastic workflows. It uses Elastic Agent Builder as the primary integration path and offers a deprecated legacy_direct fallback for environments that cannot expose the Agent Builder MCP endpoint yet. For end users, the setup flow stays the same in both modes: install the plugin, fill the Claude userConfig prompts, then ask Claude for Elastic investigations in natural language. The mode only changes which backend the plugin starts behind the scenes.

Elasticsearch

In its own words, on Official MCP Registry:

Elasticsearch MCP Server for ES 5.x-9.x with a query harness, field validation and full API access

How to run each

elastic-sense As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install elastic-sense@claude-community

Elasticsearch As a local MCP server: npm package

Claude Code
claude mcp add --env "ES_API_KEY=<YOUR_ES_API_KEY>" --env "ES_PASSWORD=<YOUR_ES_PASSWORD>" --env "ES_URL=<YOUR_ES_URL>" --env "MCP_TRANSPORT=<YOUR_MCP_TRANSPORT>" --transport stdio elasticsearch -- npx -y @tocharianou/elasticsearch-mcp

Requires: ES_API_KEY (secret), ES_PASSWORD (secret), ES_URL, MCP_TRANSPORT

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only elastic-sense asks for

  • ELASTIC_API_KEY (secret)
  • ELASTIC_MCP_URL
  • LEGACY_ES_SSL_SKIP_VERIFY
  • LEGACY_ES_URL
  • USE_LEGACY_DIRECT_MODE

Only Elasticsearch asks for

  • ES_API_KEY (secret)
  • ES_CA_CERT
  • ES_PASSWORD (secret)
  • ES_URL
  • ES_USERNAME
  • MAX_TOKEN_CALL
  • MCP_HTTP_HOST
  • MCP_HTTP_PORT
  • MCP_TRANSPORT
  • NODE_TLS_REJECT_UNAUTHORIZED

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

What it can do: elastic-sense · What it can do: Elasticsearch · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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