Ext Ops Panel
Open dashboard
Comparison

elastic-sense vs firetiger

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). firetiger is a plugin bundle for AI coding tools published by firetiger-oss. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. 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-sensefiretiger
Claude Code: claude-plugins-community Listed
Version: 1.2.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.0
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

elastic-sense vs firetiger
Factelastic-sensefiretiger
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.cloud.firetiger.com/mcp/v1)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)5, secrets among them: 1Not published
Parts of the bundle (differs)59
LicenceMITMIT
Repository (differs)github.com/ahmidbbc/elastic-sensegithub.com/firetiger-oss/claude-plugin
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-12

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.

firetiger

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

Claude Code plugin for Firetiger observability workflows and MCP-powered investigations.

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

firetiger As a Claude Code plugin

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

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

Only firetiger has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

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

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

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