Ext Ops Panel
Open dashboard
Comparison

@cognigy/plugin-engine vs lumen

@cognigy/plugin-engine is an MCP server published by Cognigy. Marketplaces we read that list it: 1 (npm registry (MCP servers)). lumen is a plugin bundle for AI coding tools published by ory. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). As of our marketplace pass on 2026-11-08. 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
Marketplace@cognigy/plugin-enginelumen
npm registry (MCP servers) Listed
Version: 1.22.6
Downloads/month (npm): 2 606
Downloads/week (npm): 1 162
Forks (GitHub): 14
Stars (GitHub): 18
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 0.0.42
Forks (GitHub): 37
Stars (GitHub): 317
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

@cognigy/plugin-engine vs lumen
Fact@cognigy/plugin-enginelumen
Marketplaces that list it11
Stars (GitHub) (differs)18 (worse)317 (better)
Forks (GitHub) (differs)14 (worse)37 (better)
Last release (differs)2026-11-06Not published
Where it runs (differs)On your machine (@cognigy/plugin-engine)Installs as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle5
Licence (differs)MITApache-2.0
Repository (differs)github.com/cognigy/cognigy-plugingithub.com/ory/lumen
Changes in the last 7 days (differs)10
First seen (differs)2026-10-122026-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

@cognigy/plugin-engine

In its own words, on npm registry (MCP servers):

MCP server engine for the NiCE Cognigy Plugin (Claude Code, Codex, and more)

lumen

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

Precise local semantic code search via MCP. Indexes your codebase with Go AST parsing, embeds with Ollama or LM Studio, and exposes vector search to Claude through an MCP server — no cloud, no npm.

How to run each

@cognigy/plugin-engine

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

lumen As a Claude Code plugin

Claude Code
/plugin install lumen@claude-plugins-official

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

Neither one's marketplaces publish the settings it asks for.

What it can do: @cognigy/plugin-engine · What it can do: lumen · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/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