Ext Ops Panel
Open dashboard
Comparison

AIPost MCP Server vs Contentrain

AIPost MCP Server is an MCP server published by AIPOST-EMAIL. Marketplaces we read that list it: 1 (Official MCP Registry). Contentrain is an MCP server published by Contentrain. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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
MarketplaceAIPost MCP ServerContentrain
Official MCP Registry Listed
Version: 1.1.1
Downloads/month (npm): 573
Downloads/week (npm): 49
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 3.11.3
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

AIPost MCP Server vs Contentrain
FactAIPost MCP ServerContentrain
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)6 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (@aipost/mcp-server)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle8
Licence (differs)Not statedMIT
Repository (differs)github.com/aipost-email/mcp-servergithub.com/contentrain/ai
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (25 h 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

AIPost MCP Server

In its own words, on Official MCP Registry:

Typed structured messaging for AI agents via AIPost.email with Ed25519 signing

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

AIPost MCP Server As a local MCP server: npm package

Claude Code
claude mcp add --env "AIPOST_API_KEY=<YOUR_AIPOST_API_KEY>" --transport stdio aipost-mcp-server -- npx -y @aipost/mcp-server -y @aipost/mcp-server

Requires: AIPOST_API_KEY (secret)

Contentrain As a Claude Code plugin

Claude Code
/plugin marketplace add contentrain/ai
/plugin install contentrain@contentrain

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

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

What it can do: AIPost MCP Server · What it can do: Contentrain · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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