Contentrain vs Chronicle MCP
Contentrain is an MCP server published by Contentrain. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Chronicle MCP is an MCP server published by Leviathan0x0. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
| Marketplace |  Contentrain |  Chronicle MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 3.11.17 Downloads/month (npm): 13 422 Downloads/week (npm): 1 470 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 1.6.2 Downloads/month (PyPI): 114 Downloads/week (PyPI): 400 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 3.11.17 Downloads/month (npm): 13 422 Downloads/week (npm): 1 470 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Not listed |
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
| Fact | Contentrain | Chronicle MCP |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 6 (better) | 3 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-28 (better) | 2026-10-25 (worse) |
| Where it runs (differs) | Remote server or your machine | On your machine (chronicle-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/contentrain/ai | github.com/leviathan0x0/chronicle-mcp |
| Changes in the last 7 days (differs) | 19 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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
Contentrain
Git-native content governance for AI agents — 27 deterministic MCP tools over stdio and HTTP.
Chronicle MCP
Local, private AI chat history search & memory: BM25 over your Cursor, Claude and ChatGPT chats.
How to run each
Contentrain As a remote MCP server
claude mcp add --transport http contentrain https://studio.contentrain.io/api/mcp/remoteChronicle MCP As a local MCP server: PyPI package
claude mcp add --transport stdio chronicle-mcp -- uvx chronicle-mcp-serverCommands 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
The marketplaces of Contentrain publish no settings it asks for, so we do not compare settings.
What it can do: Contentrain · What it can do: Chronicle MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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.