Ext Ops Panel
Open dashboard
Comparison

Product Documentation vs Contentrain

Product Documentation is a plugin bundle for AI coding tools published by eugenelim. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Contentrain is an MCP server published by Contentrain. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceProduct DocumentationContentrain
Community marketplace eugenelim/agent-ready-repo Listed
Version: 0.1.2
Forks (GitHub): 7
Stars (GitHub): 24
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.11.8
Downloads/month (npm): 14 220
Downloads/week (npm): 2 372
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

Product Documentation vs Contentrain
FactProduct DocumentationContentrain
Marketplaces that list it11
Stars (GitHub) (differs)24 (better)6 (worse)
Forks (GitHub) (differs)7 (better)0 (worse)
Last release (differs)Not published2026-10-21
Where it runs (differs)Installs as a plugin bundleRemote server (studio.contentrain.io/api/mcp/v1/%7Bproject_id%7D/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)Apache-2.0 OR MITMIT
Repository (differs)github.com/eugenelim/agent-ready-repogithub.com/contentrain/ai
Changes in the last 7 days (differs)27
First seen (differs)2026-10-182026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (4 days ago)

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

Product Documentation

In its own words, on Community GitHub marketplaces:

Documentation that matches what actually shipped. Write, restructure, or audit READMEs, quickstarts, guides, and release notes for any library, CLI, API, app, or service, with the reader's journey showing which page is missing.

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

Product Documentation As a Claude Code plugin

Claude Code
/plugin marketplace add eugenelim/agent-ready-repo
/plugin install product-documentation@agent-ready-repo

Contentrain

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

Requires: Authorization header

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

Only Contentrain 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

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

What it can do: Product Documentation · What it can do: Contentrain · Compare two other plugins

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. 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