Ext Ops Panel
Open dashboard
Comparison

llm-gateway vs Contentrain

llm-gateway is a plugin bundle for AI coding tools published by verivus-oss. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). Contentrain is an MCP server published by Contentrain. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-26. 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
Marketplacellm-gatewayContentrain
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 16
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.11.16
Downloads/month (npm): 13 422
Downloads/week (npm): 1 470
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 3.11.16
Downloads/month (npm): 13 422
Downloads/week (npm): 1 470
Forks (GitHub): 0
Stars (GitHub): 6
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

llm-gateway vs Contentrain
Factllm-gatewayContentrain
Marketplaces that list it22
Stars (GitHub) (differs)16 (better)6 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-24
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)12Not a bundle
LicenceMITMIT
Repository (differs)github.com/verivus-oss/llm-cli-gatewaygithub.com/contentrain/ai
Changes in the last 7 days (differs)017
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

llm-gateway

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

Multi-LLM orchestration MCP server. Delegate tasks to Claude Code, Codex, and Gemini CLIs with session management, retry logic, async job orchestration, and token optimization.

Contentrain

In its own words, on Official MCP Registry:

Git-native content governance for AI agents — 27 deterministic MCP tools over stdio and HTTP.

How to run each

llm-gateway As a Claude Code plugin

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

Contentrain As a remote MCP server

Claude Code
claude mcp add --transport http contentrain https://studio.contentrain.io/api/mcp/remote

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: llm-gateway · What it can do: Contentrain · 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 public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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