Ext Ops Panel
Open dashboard
Comparison

Sequa.AI vs session-metrics

Sequa.AI is an MCP server published by sequa-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). session-metrics is a plugin bundle for AI coding tools published by George Liu. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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
MarketplaceSequa.AIsession-metrics
Docker MCP Catalog Listed
Version: sha256:f4e0e271c5c5
Forks (GitHub): 5
Pulls (Docker Hub): 10 425
Stars (Docker Hub): 1
Stars (GitHub): 22
Not marked · First seen
Not listed
Community marketplace centminmod/claude-plugins Not listed Listed
Version: 1.91.0
Forks (GitHub): 2
Stars (GitHub): 18
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

Sequa.AI vs session-metrics
FactSequa.AIsession-metrics
Marketplaces that list it11
Stars (GitHub) (differs)22 (better)18 (worse)
Pulls (Docker Hub) (differs)10 425No figure on Docker Hub
Forks (GitHub) (differs)5 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sequa)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)1Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle3
LicenceMITMIT
Repository (differs)github.com/sequa-ai/sequa-mcpgithub.com/centminmod/claude-plugins
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15

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

Sequa.AI

In its own words, on Docker MCP Catalog:

Stop stitching context for Copilot and Cursor. With Sequa MCP, your AI tools know your entire codebase and docs out of the box.

session-metrics

In its own words, on Community GitHub marketplaces:

Per-turn token, cost, and cache analytics for Claude Code sessions. Multi-format export (text/JSON/CSV/MD/HTML) with session blocks, weekly roll-up, subagent attribution, dynamic-workflow tracking, and 9-category turn waste classification. HTML reports include cost timeline, hour-of-day punchcard, model-switch dividers, cache-break badges, a per-turn detail drawer, and a per-request breakdown that groups turns by the prompt that drove them. Sibling skills: audit-session-metrics audits exports for waste patterns (summarisation-only — run on /model haiku for a much cheaper run); task-breakdown groups requests into semantic tasks with worth-it / wasted verdicts and a Tasks companion page. Zero network, stdlib-only Python.

How to run each

Sequa.AI As a local MCP server: Docker image

Claude Code
claude mcp add --env "API_KEY=<YOUR_API_KEY>" --transport stdio sequa -- docker run -i --rm -e API_KEY mcp/sequa

Requires: API_KEY (secret)

session-metrics As a Claude Code plugin

Claude Code
/plugin marketplace add centminmod/claude-plugins
/plugin install session-metrics@centminmod

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

Tools each declares

The marketplaces of session-metrics publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Sequa.AI · What it can do: session-metrics · 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